Tor and Chutney CI improvements

We currently run chutney tests on every Tor and Chutney branch and pull request. We deal with non-determinism by allowing a small number of chutney failures, before reporting an overall test failure.

But sometimes failures are hard to diagnose. This ticket is a parent ticket for improvements that help us diagnose chutney failures.

changed milestone to %Tor: unspecified

added 041-deferred-20190530 042-can 044-deferred chutney component::core tor/tor consistency continuous-integration integration-testing jenkins milestone::Tor: unspecified postfreeze-ok priority::high reviewer::weasel severity::normal status::new teor-unreached-2019-03-08 test tor-ci type::enhancement labels

If we wanted to use docker for this, I did a proof of concept here: git@github.com:chelseakomlo/tor-integration-ci.git, master branch

We can also test using different OS/versions as we do with unit tests.

This runs both stem and chutney tests, but I see that we already have a stem task in jenkins, so I can change this to run only chutney tests if we want to keep them separate.

After a short chat with weasel, we talked about:

1. Docker doesn't fit into our current setup but the ideas from the docker file should translate well
2. Chutney tests should be their own task
3. Ideally we will use the tor binary that has already been built in prior tasks For 3, it looks like the location of the tor binary needs to be set by the environment variable CHUTNEY_TOR

Trac:
Component: - Select a component to Core Tor/Tor

Trac:
Milestone: N/A to Tor: 0.2.???
Keywords: N/A deleted, test added

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: N/A deleted, continuous-integration, integration-testing, consistency, jenkins, chutney added

I want to do this in 0.3.6, to catch more bugs like #27080 (moved).

As well as chelsea's implementation, meejah has a travis chutney here: https://travis-ci.org/tahoe-lafs/tahoe-lafs/jobs/417471760#L797

Trac:
Summary: Run chutney tests in Jenkins to Run chutney tests in Jenkins or Travis
Owner: N/A to teor
Milestone: Tor: unspecified to Tor: 0.3.6.x-final
Status: new to assigned

Trac:
Parent: N/A to #27230 (moved)

We should make this change to test #27146 (moved).

Trac:
Parent: #27230 (moved) to #27146 (moved)

Trac:
Parent: #27146 (moved) to N/A

#27912 (moved) is a duplicate, applying properties

Trac:
Priority: Medium to High
Milestone: Tor: 0.3.6.x-final to Tor: 0.3.5.x-final

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: 0.3.6.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

Mark some tickets as postfreeze-ok, to indicate that I think they are okay to accept in 0.4.0 post-freeze. Does not indicate that they are all necessary to do postfreeze.

Trac:
Keywords: N/A deleted, postfreeze-ok added

IIUC this is roadmapped for 0.4.1.x

Trac:
Milestone: Tor: 0.4.0.x-final to Tor: 0.4.1.x-final

I'd like to do these tickets, but not in the next few months.

Trac:
Owner: teor to N/A
Keywords: N/A deleted, teor-unreached-2019-03-08 added