14
84%
master: 98%

Ran 01 Dec 2020 11:06AM UTC

Files 152

Run time 21s

Badge

Embed ▾

Committed 30 Nov 2020 03:34PM UTC coverage: 83.297% (-8.1%) from 91.409%

Job # 2.6.1, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=2 PROTOCOL=msgpack

Build Type

push

travis-ci

Committed by

TheSmartnik

Commit Message

Use default fallback hosts when custom environment set

When environment is set in the client SDKs, we can now rely on default fallback hosts as follows.

Fallbacks are ENV-[a-e]-fallback.ably-realtime.com. For example:

ENV-a-fallback.ably-realtime.com
ENV-b-fallback.ably-realtime.com
ENV-c-fallback.ably-realtime.com
ENV-d-fallback.ably-realtime.com
ENV-e-fallback.ably-realtime.com

Note that this change:

- It breaks a lot of tests against sandbox that assumed no fallback hosts would be used
- We need to ensure that custom hosts or custom ports result do not use default environment fallback hosts.  We should only use when only the custom environment is set
- Some spec updates are needed in the spec relating to the use of fallback hosts

See related issue https://github.com/ably/docs/issues/818 (no spec yet exists)

Run Details

7989 of 9591 relevant lines covered (83.3%)

31.52 hits per line

ably / ably-ruby / 1113 / 14
84%
master: 98%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1113.14 (2.6.1, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=2 PROTOCOL=msgpack)

ably / ably-ruby / 1113 / 14 84% master: 98%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1113.14 (2.6.1, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=2 PROTOCOL=msgpack)

ably / ably-ruby / 1113 / 14
84%
master: 98%

README BADGES
x