Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #33167
Closed
Open
Created Feb 06, 2020 by juga@jugaMaintainer

Test changes in descriptors

Working on legacy/trac#30733 (moved) asn pointed out that there're no tests to check the changes in descriptors.

It'll be easier to create these tests when:

  • sbws can use chutney (legacy/trac#33150 (moved)) so that the test network lives longer than the 1st consensus
  • RelayList can be initialized with different consensus/descriptors and not only a controller (legacy/trac#29717 (moved))
  • have an external tool that check the generated bandwidth files in the Tor network and detects changes in the descriptors (legacy/trac#33152 (moved))

Maybe we should include this ticket as part of legacy/trac#33121 (moved)

Assignee
Assign to
Time tracking