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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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
  • #34037

Closed (moved)
Open
Opened Apr 28, 2020 by teor@teor

Make chutney check tor's logs for reachability self-test success

This ticket is an alternative to #33582 (moved) or #33222 (moved).

Instead of fixing bridge descriptor uploads, we can check bridge logs to make sure that reachability self-tests have succeeded.

For consistency, we should also do the same checks for relays.

We can only do these tests on authorities, relays, and bridges that are configured with AssumeReachable 0. Chutney's current defaults are:

  • directory authorities: 1
  • bridge authorities: 1
  • relays: 0
  • bridges: 0
  • clients: clients never perform reachability self-tests

Some custom chutney networks may set AssumeReachable 1 for relays and bridges. So we should make it easy for them to disable these checks.

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