Issue metadata
Sign in to add a comment
|
bot affinity 'build139-m1' is broken on chromium.perf/Win 7 x64 Perf, affecting 26 tests |
||||||||||||||||||||||
Issue descriptionbot affinity 'build139-m1' is broken on chromium.perf/Win 7 x64 Perf, affecting 26 tests Builders failed on: - Win 7 x64 Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf "shard #0 expired, not enough capacity"
,
Oct 9 2017
,
Oct 10 2017
,
Oct 10 2017
,
Oct 11 2017
re-opening as apparently there are still issues with this host (currently down).
,
Oct 12 2017
The machine is completely broken. Because this is perf, I assume it needs to remain bare metal, and of the same *exact* specifications? Any wiggle room here? Thanks.
,
Oct 12 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome-golo/chrome-golo/+/5a3b2ac5bd533b972256c9c810d330a1c82daa13 commit 5a3b2ac5bd533b972256c9c810d330a1c82daa13 Author: John Weathersby <johnw@google.com> Date: Thu Oct 12 21:23:35 2017
,
Oct 12 2017
#6: +sullivan should know for sure, but I assume so.
,
Oct 12 2017
Managed to find a carbon-copy replacement. at some point we might want to talk about refreshing the fleet, mostly because these are all out of warranty. For now, this bot is back up. Thanks.
,
Oct 12 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by friedman@chromium.org
, Oct 9 2017Status: Assigned (was: Available)