bot affinity 'build103-m1', 'build104-m1', 'build105-m1' is broken on chromium.perf/Win 7 ATI GPU Perf, affecting 83 tests |
||||||
Issue descriptionbot affinity 'build103-m1', 'build104-m1', 'build105-m1' is broken on chromium.perf/Win 7 ATI GPU Perf, affecting 83 tests Builders failed on: - Win 7 ATI GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf - Win 7 ATI GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf - Win 7 ATI GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf - Win 7 ATI GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf - Win 7 ATI GPU Perf: https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf
,
Nov 27 2017
,
Nov 27 2017
I'm assigning to Sean, to reassign as needed. It looks like this is automatically reported by SOM, but there is no information about what to do. Could we add that to the automatically generated ticket? Also, I don't know what to do. I've brought it up in chat, so hopefully someone will help. Otherwise, can you let me know what do to, or reassign to someone who knows?
,
Nov 27 2017
Labs should look at these machines and fix them. I've assigned it to vhang to triage. Hopefully this should be enough information for you to fix. Sean and/or tiffany, I didn't know SOM was auto filing these?
,
Nov 27 2017
Labs should fix the one of the three that are problematic and fix it (build105-m1) Which I just did.
,
Nov 27 2017
Martiniss: Sheriff-o-Matic shouldn't autofile bugs completely. A new feature to file bugs through the Sheriff-o-Matic UI recently launched, which allows sheriffs to file bugs in SoM and have them autolinked to the alert they filed on, but they're filed through a service account rather than the bug filer. Filed a quick bug for the SoM fix to make it easier to find information on the bug filer: https://bugs.chromium.org/p/chromium/issues/detail?id=788825
,
Dec 5 2017
,
Dec 21 2017
What's left to do here?
,
Feb 23 2018
I think Peter fixed the problem in comment #5. I'm going to mark this fixed but reopen if there's still a problem. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by altimin@chromium.org
, Nov 27 2017