All jobs shard on build121-b swarming bot from Win 10 High-DPI Perf are faling with "expired, not enough capacity" |
|||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf/builds/342 Bot status indicates that there were no tests ran after 02/17/2017 https://chromium-swarm.appspot.com/bot?id=build121-b1&sort_stats=total%3Adesc
,
Mar 13 2017
cc: sulllivan@ (crbug is warning that eyaich@ has been away for a while) - just searching for a bot owner to take a look.
,
Mar 13 2017
,
Mar 13 2017
,
Mar 24 2017
Can the trooper take a look at build121-b1? After increasing timeouts, we're seeing all 56 expired tasks on the builder going to this shard: https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf/builds/431 Is there something wrong with the bot?
,
Mar 24 2017
This bot is being worked on here: https://bugs.chromium.org/p/chromium/issues/detail?id=704735 The last time this bot had an issue, the suggestion was to take one from the tryserver pool to replace it. See: https://bugs.chromium.org/p/chromium/issues/detail?id=693280#c11 Is that still an option?
,
Mar 24 2017
Yes, definitely take one from the tryserver pool. Thanks!
,
Mar 24 2017
Targeting build180-b4, since it's not doing anything at the moment.
,
Mar 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/6ce4b71b2e26bf6504c2d128f2a07cfce85df301 commit 6ce4b71b2e26bf6504c2d128f2a07cfce85df301 Author: John Weathersby <johnw@google.com> Date: Fri Mar 24 21:13:59 2017 Removing build180-b4 (converting to swarming) BUG=704735, 695613 Change-Id: I2e38b2aaabf850e6a0338b9671d1237c99a96487 Reviewed-on: https://chromium-review.googlesource.com/458987 Reviewed-by: Stephen Martinis <martiniss@chromium.org> Commit-Queue: John Weathersby <johnw@chromium.org> [modify] https://crrev.com/6ce4b71b2e26bf6504c2d128f2a07cfce85df301/masters/master.tryserver.chromium.perf/slaves.cfg
,
Mar 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/6ce4b71b2e26bf6504c2d128f2a07cfce85df301 commit 6ce4b71b2e26bf6504c2d128f2a07cfce85df301 Author: John Weathersby <johnw@google.com> Date: Fri Mar 24 21:13:59 2017 Removing build180-b4 (converting to swarming) BUG=704735, 695613 Change-Id: I2e38b2aaabf850e6a0338b9671d1237c99a96487 Reviewed-on: https://chromium-review.googlesource.com/458987 Reviewed-by: Stephen Martinis <martiniss@chromium.org> Commit-Queue: John Weathersby <johnw@chromium.org> [modify] https://crrev.com/6ce4b71b2e26bf6504c2d128f2a07cfce85df301/masters/master.tryserver.chromium.perf/slaves.cfg
,
Mar 24 2017
build180-b4 is in swarming now. I'm not sure what magic needs to happen to get it into the Chrome-perf pool. martiniss, can you help with that part?
,
Mar 28 2017
I believe this needs a source side CL, and a change in the swarming config. I'll make both CLs.
,
Mar 28 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/infradata/config/+/45022250fd79e8ef08b36e2546cf03acc3c52d5a commit 45022250fd79e8ef08b36e2546cf03acc3c52d5a Author: Stephen Martinis <martiniss@google.com> Date: Tue Mar 28 20:26:53 2017
,
Mar 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/93769dd7d7709ef72a71ef59d0ae9bbcfc0567b1 commit 93769dd7d7709ef72a71ef59d0ae9bbcfc0567b1 Author: martiniss <martiniss@chromium.org> Date: Wed Mar 29 19:38:57 2017 Add new bot to Win 10 High-DPI Perf BUG= 695613 Review-Url: https://codereview.chromium.org/2784633002 Cr-Commit-Position: refs/heads/master@{#460494} [modify] https://crrev.com/93769dd7d7709ef72a71ef59d0ae9bbcfc0567b1/testing/buildbot/chromium.perf.json [modify] https://crrev.com/93769dd7d7709ef72a71ef59d0ae9bbcfc0567b1/tools/perf/core/perf_data_generator.py
,
Apr 10 2017
Adding the new bot in #14 fixed this. Closing. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by chcunningham@chromium.org
, Mar 13 2017