Nuts+Bolts 09-Sep-2014

[Brian Warner]

Attendees: Brian, Daira.

We spent the whole time successfully(!) getting Travis and Coveralls set
up. The github project page[1] now has a pair of image badges: one for
Travis-CS[2] which shows that the most recent 'master' commit is
(hopefully) passing the test suite, and a second for Coveralls.io[3]
which shows how much code the test suite actually exercises.

Coveralls reports a coverage of 92%. It's actually a bit higher than
that (maybe 95%) because it currently thinks that every file in the
test/ subdirectory is real code, even though many of them are utilities
for other kinds of tests (like benchmarks and memory-footprint tools)
that aren't run during the normal test suite. When we were tracking
code-coverage before (via buildbot), we told the tool to ignore this
whole directory. We decided to leave it in, for a little while, because
it can reveal when test cases aren't executing the way we think they
should. Ideally, we'd convince coveralls to display those files but not
count them towards the total numbers.

Since last week, we finished off a number of the issues blocking the
1.11 release. We still have 17 tickets left in the milestone[4], some
small, some large. The two biggest clusters are surrounding "upload
happiness" (#1124, #1130, #1382, #1830, #1814), and a particularly weird
crash involving the find-my-own-IP-address on OS-X and some BSD systems
(#2023).

I'm hoping to find a small fix for #2023 for 1.11, then in the 1.12
cycle I'd like to rip out iputil entirely, and either have the
Introducer help determine external IP addresses for server nodes, or
require server admins to configure addresses manually.

I'm also hoping to overhaul the way setup.py works (with installing
things into support/, creating bin/tahoe from a template, and using
subprocess.call to execute the real entrypoint with a new
$PATH/$PYTHONPATH). We have at least two branches experimenting with
virtualenv-based replacements, and I think we should be able to switch
to one of them early in the 1.12 cycle. We will need help with windows
and mac user-oriented packaging.

cheers,
 -Brian


[1]: https://github.com/tahoe-lafs/tahoe-lafs
[2]: https://travis-ci.org/tahoe-lafs/tahoe-lafs
[3]: https://coveralls.io/r/tahoe-lafs/tahoe-lafs?branch=master
[4]:
https://tahoe-lafs.org/trac/tahoe-lafs/query?status=assigned&status=new&status=reopened&group=status&milestone=1.11.0