Opened 2 years ago

Last modified 5 weeks ago

#20647 assigned enhancement

Run chutney tests in Jenkins or Travis

Reported by: chelseakomlo Owned by: teor
Priority: High Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: test, chutney, consistency, jenkins, integration-testing, continuous-integration
Cc: Actual Points:
Parent ID: Points:
Reviewer: weasel Sponsor:

Description

It would be nice for chutney tests to be run on every build.

However, because chutney tests cannot be entirely deterministic (although we can do more work to get them closer), this probably should not block the build if tests fail (at least for the short term & we eliminate as much flakiness as possible).

Child Tickets

TicketTypeStatusOwnerSummary
#20473defectnewFix Chutney Nodes that don't bootstrap
#21573defectnewFix tor warnings that chutney is currently ignoring
#22132defectneeds_revisionChutney should avoid waiting for set times: wait for conditions instead
#22133enhancementnewWhen CHUTNEY_DEBUG is set, make tor log a debug log
#27912enhancementneeds_revisionteorAdd travis CI for the Chutney repository
#27965defectclosedteorChutney's single-onion-ipv6-md test fails on master
#28013enhancementassignedcatalystrun test-network-all in Travis CI
#28192defectnewWork out why 0.3.5 and later fail chutney (but 0.3.4 and earlier do not)
#28204defectnewMake chutney log the verify progress for each circuit
#28220enhancementnewCreate a chutney network with a single authority, and make sure it bootstraps

Change History (15)

comment:1 Changed 2 years ago by chelseakomlo

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.

comment:2 Changed 2 years ago by chelseakomlo

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

comment:3 Changed 2 years ago by chelseakomlo

Component: - Select a componentCore Tor/Tor

comment:4 Changed 2 years ago by dgoulet

Keywords: test added
Milestone: Tor: 0.2.???

comment:5 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:6 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

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

comment:7 Changed 19 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:8 Changed 18 months ago by nickm

Keywords: chutney consistency jenkins integration-testing continuous-integration added

comment:9 Changed 4 months ago by teor

Milestone: Tor: unspecifiedTor: 0.3.6.x-final
Owner: set to teor
Status: newassigned
Summary: Run chutney tests in JenkinsRun chutney tests in Jenkins or Travis

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

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

comment:10 Changed 4 months ago by teor

Parent ID: #27230

comment:11 Changed 4 months ago by teor

Parent ID: #27230#27146

We should make this change to test #27146.

comment:12 Changed 2 months ago by teor

Parent ID: #27146

comment:13 Changed 2 months ago by teor

Milestone: Tor: 0.3.6.x-finalTor: 0.3.5.x-final
Priority: MediumHigh

#27912 is a duplicate, applying properties

comment:14 Changed 2 months ago by catalyst

Milestone: Tor: 0.3.5.x-finalTor: 0.3.6.x-final

comment:15 Changed 5 weeks ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

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

Note: See TracTickets for help on using tickets.