Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #31331

Closed (moved)
(moved)
Open
Created Aug 04, 2019 by juga @juga

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking