Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #29703

Closed (moved)
(moved)
Open
Created Mar 08, 2019 by teor@teor

Backport test-network.sh fixes to 0.2.9

In our 0.3.4 chutney CI, we get the chutney version of test-network.sh:

test-network.sh: using CHUTNEY_DNS_CONF '/dev/null'
test-network.sh: $TOR_DIR not set, trying $PWD
test-network.sh: $TOR_DIR is a Tor 0.3.4 or earlier build directory

https://travis-ci.org/torproject/tor/jobs/499382754#L3067

But in 0.2.9, we get the tor version of test-network.sh:

test-network.sh: Parsing command-line arguments to find $CHUTNEY_PATH
test-network.sh: $TOR_DIR not set, trying $PWD

Launching chutney using Python 2.7.6

https://travis-ci.org/torproject/tor/jobs/499382330#L2859

But tor 0.2.9's test-network.sh is meant to call chutney's test-network.sh.

We should fix this bug to make sure that we're getting consistent results from our CI. There are a lot of extra bug fixes in the latest chutney's test-network.sh, that aren't in tor 0.2.9's test-network.sh.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking