• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ably / ably-ruby / 1037 / 8
98%
master: 98%

Build:
Build:
LAST BUILD BRANCH: error-inline-updates-ably-ruby-1756019885815
DEFAULT BRANCH: master
Ran 03 May 2019 11:35AM UTC
Files 174
Run time 10s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 May 2019 10:48AM UTC coverage: 98.333% (-0.04%) from 98.377%
2.1.10, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack

push

travis-ci

mattheworiordan
Simplify msgSerial handling

There is no need to rewind msgSerial because a connection recovers or not successfully.  Rolling back is dangerous because of queued messages. Instead, operate on the basis that if a msgSerial is provided in a recovery key, then use that msgSerial regardless of whether that connection recovers or not.  This is the safest approach ensuring messages are always published when the connection is established, and not de-duped because of existing serial numbers.

16515 of 16795 relevant lines covered (98.33%)

2676.37 hits per line

Source Files on job 1037.8 (2.1.10, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack)
  • Tree
  • List 0
  • Changed 82
  • Source Changed 4
  • Coverage Changed 81
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 958
  • Travis Job 1037.8
  • 3b6d9ccd on github
  • Prev Job for 2.1.10, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack on issues/msg-serial-reset-bug-issue-179 (#1035.8)
  • Next Job for 2.1.10, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack on issues/msg-serial-reset-bug-issue-179 (#1039.8)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc