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
  • #31331
Closed
Open
Created Aug 04, 2019 by juga@jugaMaintainer

scanner integration test fails some times because the test Web server is not multi-threaded

Because the Python Web server used for the integration tests is not multi-threaded, some relays' circuits timeout. Most of the cases, this is desired since in a public network this would happen too. It is not desired in the case that the integration test check for a concrete relay measurement success, which is tests/integration/core/test_scanner.py::test_measure_relay_with_maxadvertisedbandwidth (https://travis-ci.org/torproject/sbws/jobs/565274602#L1971). This case can be solved by checking the descriptor bandwidth, not the measurement. Ideally, the Python Web server should be changed to be multi-threaded and shutting down some relays for the cases where the tests check failures.

Assignee
Assign to
Time tracking