5
84%
master: 98%

Ran 21 Feb 2020 10:29AM UTC

Files 115

Run time 22s

Badge

Embed ▾

Committed 21 Feb 2020 09:19AM UTC coverage: 91.519% (+0.02%) from 91.498%

Job # 2.5.5, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=2 PROTOCOL=json

Build Type

push

travis-ci

Committed by

mattheworiordan

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

8838 of 9657 relevant lines covered (91.52%)

781.57 hits per line

ably / ably-ruby / 1085 / 5
84%
master: 98%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1085.5 (2.5.5, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=2 PROTOCOL=json)

ably / ably-ruby / 1085 / 5 84% master: 98%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1085.5 (2.5.5, RSPEC_RETRY=true PARALLEL_TEST_PROCESSORS=2 PROTOCOL=json)

ably / ably-ruby / 1085 / 5
84%
master: 98%

README BADGES
x