Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #16952

Closed (moved)
Open
Opened Sep 01, 2015 by teor@teor

Retry configure/verify on transient chutney failures

chutney occasionally fails to bootstrap or verify. Sometimes, and on some platforms / machines, bootstrap is slower than we expect.

We should either: fix intermittent failures (#16951 (moved)), or lengthen the default sleep time (this ticket), or retry up to N times (argument) (this ticket) with increasing sleep times (this ticket), or implement a chutney command that finds out whether the network has finished bootstrapping (#16950 (moved)).

Easy fixes are to: make the default sleep time 30 seconds; retry verify at 45 and 60 seconds before giving up (args for interval and number of retries); and then retry once from the start with a new network in case of chutney configure / launch failure (arg for number of reconfigures). This will make it a maximum of 4.5 minutes before the test fails, after 3 x 2 retries.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#16952