Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 972
    • Issues 972
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #9521
Closed
Open
Issue created Jun 02, 2015 by anonym@anonymMaintainer

Use the chutney Tor network simulator in our test suite

Originally created by @anonym on #9521 (Redmine)

See parent ticket (#9519 (closed)) for the rationale.

We may want to use chutney to simulate the Tor network for increased determinism in our test suite.

The Tor network is a large part of the test suite’s indeterminism, both from transient network issues when communicating with the Tor network (or internal issues, e.g. bad circuits), and from the chosen exit node being blocked. Simulating the Tor network on the testing host would eliminate all such issues.

There is, however, a potential for making the testing host blacklisted/blocked if services identifies the repeated connections as spam (example: irc.oftc.net blocks lizard because of the multiple IRC connections made per hour, potentially). If that is a problem, #9520 (closed) would solve that.

Feature Branch: test/9521-chutney

Parent Task: #9519 (closed)

Related issues

  • Related to #9478 (closed)
  • Related to #9520 (closed)
  • Related to #11356 (closed)
  • Blocks #10442 (closed)
  • Blocks #10381 (closed)
  • Blocks #10379 (closed)
  • Blocks #10376 (closed)
  • Blocks #10497 (closed)
  • Blocks #10495 (closed)
  • Blocks #11351 (closed)
  • Blocks #9654 (closed)
  • Blocks #10440 (closed)
Edited May 15, 2020 by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking