why are covered lines changing from build to build?

[daira]

E.g. see the changed files in ​https://coveralls.io/builds/1188907, which is a doc-only commit.

[daira]

zooko: Does anybody know why coveralls say that coverage decreased here? ​https://github.com/tahoe-lafs/tahoe-lafs/pull/110#issuecomment-56559949

zooko: Better yet, can I find a diff of coverage before and after that PR?

warner: the coveralls site shows which files are up/down (or both at the same time, weirdly)

warner: it's not as readable as it could be

*zooko looks at ​https://coveralls.io/builds/1246883

zooko: So this page ​https://coveralls.io/builds/1246883 is all about this one PR.

warner: looks like 5 lines in mutable/publish.py ..

*zooko looks at ​https://coveralls.io/files/297721106

warner: urgh, it shows which lines are covered/uncovered, and how many changed, but it doesn't say *which* lines changed

zooko: Oh cool there's a button to "previous job": ​https://coveralls.io/files/290358568

zooko: Now I flip back and forth until I see it... :-)

zooko: line 451

zooko: That's 3 of the lines ...

warner: one job had some bad shares, the other didn't

zooko: This process of spotting the difference needs automation. :-(

warner: yeah

warner: two more lines at 496

warner: which is the same thing, lack of bad shares

[exarkun]

The tools are a problem, yes. coveralls.io has garbage collected a lot of the details of the builds linked in the above conversation, though. This ticket is not actionable.