12
98%
master: 98%

Ran 03 May 2019 12:11PM UTC

Files 174

Run time 12s

Badge

Embed ▾

Committed 03 May 2019 11:13AM UTC coverage: 98.291% (+5.2%) from 93.05%

Job # 2.6.3, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack

Build Type

Pull #181

travis-ci

Committed by

web-flow

Commit Message

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.

Pull Request Pull Request #181: msgSerial fixes including connection recovery fix

Run Details

16504 of 16791 relevant lines covered (98.29%)

2921.8 hits per line

ably / ably-ruby / 1038 / 12
98%
master: 98%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1038.12 (2.6.3, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack)

ably / ably-ruby / 1038 / 12 98% master: 98%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1038.12 (2.6.3, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=4 PROTOCOL=msgpack)

ably / ably-ruby / 1038 / 12
98%
master: 98%

README BADGES
x