DUTs not getting assigned jobs |
||
Issue description
Since yesterday, I'm trying to run tests in the jetstream-test pool of whirlwind devices in the Destiny lab.
This was working fine until some time early this morning, when 4 of the 5
DUTs in this pool stopped running jobs. There is now a backlog of jobs
queued, but only one DUT is accepting jobs.
The DUTs not taking jobs are:
chromeos4-row10-jetstream-host10
chromeos4-row10-jetstream-host11
chromeos4-row10-jetstream-host12
chromeos4-row10-jetstream-host14
The DUT that is taking jobs is
chromeos4-row10-jetstream-host9
The DUTs have Status=Ready and Locked=No and seem to have appropriate board:whirlwind, pool:jetstream-test,
and cros_version labels, so I don't know why these would not be getting scheduled.
Some of the DUTs show the last queued job as servohost_Reboot, invoked by
chromeos-test.
,
Oct 7 2016
pool:jetstream-test Example DUT: https://ubercautotest.corp.google.com/afe/#tab_id=view_host&object_id=5598 Example of queued test that is not getting run on this DUT even though it is available: https://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=79632305
,
Oct 7 2016
Looks like this has cleared up. Possible user error in creating recurring run. |
||
►
Sign in to add a comment |
||
Comment 1 by akes...@chromium.org
, Oct 7 2016