Ok, we should work out a policy to decide which existing tests need to be marked with.
I want to limit to only checking bots that affect the main waterfall and cq. So those are would be:
chromium.linux:Android Tests
chromium.linux:Android Tests (dbg)
chromium.android:Android Swarm Builder
I also see "chromium.android:Android N5X Swarm Builder" now. Is that going to be promoted to cq soon too? Should I take that into account as well?
For policy, how about: any red/grey box on the flakiness dashboard means the test needs to be marked RetryOnFailure. I'd like some better criteria like "no flake in last 100 runs", but I don't know how flakiness dashboard tracks number of runs, when it drops old data etc..
Is there any way I can get this raw data? Manually parsing flakiness dashboard is kinda.. manual.
The suites we should care about looking at for now would be:
- android_webview_test_apk
- blimp_test_apk
- chrome_public_test_apk
- chrome_sync_shell_test_apk
- content_shell_test_apk
We may have to do some dremel work for the raw data.
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by boliu@chromium.org
, Jun 10 2016