Test jobs sometimes get scheduled on a busy isotester while there are available ones
While investigating #10601, 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-note_5 for details.
Feature Branch: jenkins-jobs:SponsorS-leftovers, puppet-tails:SponsorS-leftovers
Related issues
- Related to #10215 (closed)
- Related to #10601
- Related to #16959
- Related to #9486 (closed)
- Related to #17216
-
Blocked by #10068 (closed)
Original created by @bertagaz on 11295 (Redmine)
Edited by intrigeri