Tryjobs stuck in Buildbucket queue |
|||
Issue descriptionhttps://apis-explorer.appspot.com/apis-explorer/?base=https://cr-buildbucket.appspot.com/_ah/api#p/buildbucket/v1/buildbucket.get?id=8956928802920542368&_h=1& This tryjob was scheduled at 01/19/2018 @ 03:21pm (PST), and is still not started yet. The command used to run is >cros tryjob -p chromiumos/third_party/autotest:poison -p chromiumos/third_party/autotest:vm_retry betty-paladin-tryjob and >cros tryjob -p chromiumos/third_party/autotest:vm_retry betty-paladin-tryjob
,
Jan 20 2018
,
Jan 25 2018
i didn't look into the master logs yet, but the build has started and completed
,
Jan 25 2018
I think this was a resource issue, we only had 2 bots available, but Don has enabled more. We can probably close this and re-open if we see any additional issues.
,
Jan 25 2018
The tryjobs in question were scheduled against the buildbot waterfall, which has many more bots, but which sees heavy use.
,
Feb 2 2018
I think this was just temporary load. |
|||
►
Sign in to add a comment |
|||
Comment 1 by jinjingl@chromium.org
, Jan 20 2018