#30064 closed defect (fixed)

Chutney often fails because Tor hasn't bootstrapped yet

Reported by: teor Owned by: teor
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: chutney-ci, network-team-roadmap-2019-Q1Q2
Cc: teor Actual Points: 0.3
Parent ID: #29729 Points: 0.5
Reviewer: nickm Sponsor: Sponsor19


Travis appears to be under heavy load right now, so we're getting about one bootstrap failure per pull request:

There's two ways to fix this issue:

  1. allow 120 seconds for bootstrap
  2. make the network run with 10 second consensus intervals

Option 1 is easy.
Option 2 might lead to some instability, but it's worth trying.

Child Tickets

Change History (5)

comment:1 Changed 16 months ago by teor

Actual Points: 0.2
Reviewer: nickm
Status: assignedneeds_review
  1. See https://github.com/torproject/chutney/pull/19
    • TODO: update the README with the new default (conflicts with #30059)
  2. See https://github.com/torproject/chutney/pull/20

comment:2 Changed 16 months ago by nickm

Status: needs_reviewmerge_ready

Both seem okay to me.

comment:3 Changed 16 months ago by teor

I'm going to merge https://github.com/torproject/chutney/pull/19 and update the README.

If we're still having issues, I might merge ​https://github.com/torproject/chutney/pull/20.

comment:4 Changed 16 months ago by teor

Merged to master, then added a commit to update the README.

I merged #30059, #30063, #30064, and #30065, then pushed.

Leaving this ticket open, in case I need ​https://github.com/torproject/chutney/pull/20.

comment:5 Changed 16 months ago by teor

Actual Points: 0.20.3
Resolution: fixed
Status: merge_readyclosed

It looks like we don't need that extra pull request.

Note: See TracTickets for help on using tickets.