SOM: Chromium PFQ informational failures is missing recent failures |
||||||
Issue descriptionProblem with Sheriff-o-Matic As of now (11:23 Pacific) it doesn't show this failure: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/cyan-tot-chrome-pfq-informational/builds/2562 That build failed at 03:32 this morning. However, there was a subsequent green build. This builder is highly flaky, failing about 50% of the time, so the issue needs investigation. SoM should show flaky builds.
,
May 8 2017
,
May 8 2017
No, we don't use chromium-try-flakes.appspot.com. How does it work? My plan is to implement crbug.com/693662 to help with this.
,
May 8 2017
+sergiyb who I believe can explain chromium-try-flakes.
,
May 9 2017
In short, the chromium-try-flakes app searches for pairs of failed and passed builds of the same builder on all patchsets in CQ. Each pair is a flake and when enough flakes are found, chromium-try-flakes files a bug into the sheriff queue on SoM, e.g. http://crbug.com/719186 . The app is currently being rewritten to support projects other than Chromium (tracked in issue 704839). Once this work is done, I'll be happy to explore what else needs to be done to add support for ChromeOS.
,
May 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 9 2018
,
Aug 2
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by seanmccullough@chromium.org
, May 8 2017Status: Available (was: Untriaged)