Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sysadmin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • tails
  • sysadmin
  • Issues
  • #11295

Test jobs sometimes get scheduled on a busy isotester while there are available ones

Originally created by @bertagaz on #11295 (Redmine)

While investigating #10601 (closed), we discovered that sometimes after a reboot_job completed, rather than starting the test job that triggered it for this isotester, Jenkins assigns this same isotester to another test job, resulting in the first test job waiting for hours for the other one to be over. See #10601 (comment 68441) for details.

Related issues

  • Related to tails#10215 (closed)
  • Related to #10601 (closed)
  • Related to tails#16959 (closed)
  • Related to #9486 (closed)
  • Related to #17216
  • Blocked by #10068 (closed)
Edited May 15, 2020 by bertagaz
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking