1
89%
master: 89%

Ran 08 Dec 2016 05:26AM UTC

Files 64

Run time 3s

Badge

Embed ▾

Committed 08 Dec 2016 05:20AM UTC coverage: 88.807% (-0.02%) from 88.824%

Job # 326.1

Build Type

push

travis-ci

Committed by

warner

Commit Message

getConnectionInfoForFURL: tolerate unparseable FURLs

There's a Tahoe test case that launches a node with a FURL of "None" (a
string), and was depending upon being able to start a Reconnector against
this without complaints. Reconnector._connect() now parses the FURL (as a
side-effect of stashing the initial ConnectionInfo object), which threw a
ValueError when "None" didn't start with "pb://".

This changes getConnectionInfoForFURL() to return None for unparseable FURLs,
which makes sense anyways, and happens to keep that test case working.

Run Details

7910 of 8907 relevant lines covered (88.81%)

0.89 hits per line

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

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 326.1

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

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 326.1

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

README BADGES
x