Opened 8 months ago

Closed 8 months ago

#32630 closed task (fixed)

Chutney Travis: Make chutney work on Bionic images

Reported by: teor Owned by: teor
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: chutney-ci
Cc: Actual Points: 0.4
Parent ID: #32240 Points: 0.1
Reviewer: nickm Sponsor:

Description

If we fix #32240 in Tor, we should do the same thing for Chutney's Travis config.

Child Tickets

TicketStatusOwnerSummaryComponent
#32631closedteorChutney Travis: Use the latest dependenciesCore Tor/Chutney
#32757closedteorTravis: Update the pypy builds for chutneyCore Tor/Chutney
#32758closedteorTravis: Update the macOS image for chutneyCore Tor/Chutney

Change History (17)

comment:1 Changed 8 months ago by teor

chutney's CI works on xenial:

So it will probably work on bionic:

This ticket may be "worksforme", just waiting on CI to confirm.

comment:2 Changed 8 months ago by teor

chutney's CI fails on bionic, with CHUTNEY_NET_DIR set to a temporary directory in /tmp:
https://travis-ci.org/teor2345/chutney/jobs/618413136#L1607

comment:3 Changed 8 months ago by teor

Summary: Chutney Travis: Make chutney work on Xenial and Bionic imagesChutney Travis: Make chutney work on Bionic images

comment:4 Changed 8 months ago by teor

Once #32721 merges, we can fix this chutney CI issue by:

  • setting CHUTNEY_TOR_SANDBOX=0 in the travis env vars
  • changing the Linux image to bionic

comment:5 Changed 8 months ago by teor

Actual Points: 0.1
Component: Core Tor/TorCore Tor/Chutney

comment:6 Changed 8 months ago by teor

Owner: set to teor
Reviewer: nickm
Status: newassigned

See my PR:

I copied across some other minor updates from fallback-scripts and tor Travis, in separate commits. See the child tickets and commit messages for details.

comment:7 Changed 8 months ago by teor

Status: assignedneeds_review

comment:8 Changed 8 months ago by nickm

CI seems to be failing here; is that expected?

comment:9 Changed 8 months ago by nickm

Otherwise, all the changes here look okay to me.

comment:10 Changed 8 months ago by teor

Status: needs_reviewneeds_revision

No, CI shouldn't fail.

There are two issues with this ticket:

  • it looks like the sandbox env var isn't working
  • the config for pypy is wrong, I also need to specify a xenial package line

There's another issue with the diagnostics here:

  • we don't show the torrc, and we don't show notice-level logs, so I can't check how the Sandbox option is configured

comment:11 Changed 8 months ago by teor

There are also some conflicts and duplicate commits with #32631, I think I'll rebase on that ticket.

comment:12 Changed 8 months ago by teor

Status: needs_revisionneeds_review

Here's my rebased PR, with fixed configs, and better diagnostics. It might still fail:

comment:14 Changed 8 months ago by teor

There were two env: keys. Sometimes I just can't yaml. I *think* CI should pass this time.

I pushed a fixup to the original PR.

Here's a squashed version for merging:

comment:15 Changed 8 months ago by nickm

Status: needs_reviewneeds_revision

pull 44 is still failing. But please feel free to merge once CI is passing and you're satisfied with it.

comment:16 Changed 8 months ago by teor

We're down to one failing job now, so that's progress.

comment:17 Changed 8 months ago by teor

Actual Points: 0.10.4
Resolution: fixed
Status: needs_revisionclosed

The 0.2.9 job was failing because it was built with OpenSSL 1.1.0g, but running with OpenSSL 1.1.1. I downgraded it to Xenial, and that fixed the issue.

Merged to master.

Note: See TracTickets for help on using tickets.