1
89%
master: 89%

Ran 01 Sep 2016 07:56PM UTC

Files 63

Run time 12s

Badge

Embed ▾

Committed 01 Sep 2016 07:51PM UTC coverage: 88.655% (+0.006%) from 88.649%

Job # 283.1

Build Type

push

travis-ci

Committed by

warner

Commit Message

allocate_tcp_port: avoid loopback-bound sockets

I thought I'd fixed this, but I'm still seeing occasional failures,
where another process has bound a socket to 127.0.0.1, and
allocate_tcp_port() gives it to me anyways. I wouldn't be surprised if
the code that's using the socket is binding it to lo0 too, otherwise it
might not cause a problem.

I think the fix is for allocate_tcp_port() to attempt to bind a
socket (with the proposed port number) to both 0.0.0.0 and then
127.0.0.1, seeing if either gives us an error.

(re) closes ticket:258

Run Details

7736 of 8726 relevant lines covered (88.65%)

0.89 hits per line

warner / foolscap / 283 / 1
89%
master: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 283.1

warner / foolscap / 283 / 1 89% master: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 283.1

warner / foolscap / 283 / 1
89%
master: 89%

README BADGES
x