Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 938
    • Issues 938
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • 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
  • #9515

Improve test suite robustness vs transient network errors

Originally created by @anonym on #9515 (Redmine)

The amount of false positives we get from tests failing due to transient network errors (e.g. Tor being slow, Exit node blocking, the live destination servers having issues etc.) is already problematic, and is blocking deployment in our Jenkins infrastructure (#8539 (closed)). Let’s make the tests must susceptible to these issues simulate a user retrying (in a suitable manner) whenever such errors occur.

Parent Task: #8539 (closed)

Subtasks

  • #9516 (closed)
  • #9517 (closed)
  • #9518 (closed)
  • #9668 (closed)
  • #9715 (closed)

Related issues

  • Related to #9478 (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