972
90%
master: 91%

Ran 17 Aug 2016 03:32PM UTC

Jobs 1

Files 16

Run time 2s

Badge

Embed ▾

pending completion

Build # 972

Build Type

push

travis-ci

Committed by

kozlovic

Commit Message

Add defensive code when returning server's client connect URL

We saw a case where a Windows VM would return 0.0.0.0 in the INFO
protocol. After debugging, it appeared that the VM had an issue
and a reboot solved it, but while in bad mode, the resolution of
the IP address would not return an error, but nothing was added
to the array and we ended-up adding at the last resort the 0.0.0.0
IP. This is a problem for Windows clients since they can't use
that IP to connect.
We could simply do nothing and the client would fail to reconnect
using this IP - which is fine -, but this is masking the real issue,
so deciding to panic when detecting this situation.

/cc @derekcollison @ColinSullivan1

Run Details

4812 of 5332 relevant lines covered (90.25%)

2709.58 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
2	972.2	17 Aug 2016 03:32PM UTC	16	90.25	Travis Job 972.2

Source Files on build 972

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

nats-io / gnatsd / 972
90%
master: 91%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 972

nats-io / gnatsd / 972 90% master: 91%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 972

nats-io / gnatsd / 972
90%
master: 91%

README BADGES
x