"ResourceFetcherTests.ResourceFetcherDidFail" is flaky |
|||||
Issue description"ResourceFetcherTests.ResourceFetcherDidFail" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyNgsSBUZsYWtlIitSZXNvdXJjZUZldGNoZXJUZXN0cy5SZXNvdXJjZUZldGNoZXJEaWRGYWlsDA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Mar 10 2017
Changwan, could you please triage this issue to a proper owner?
,
Mar 10 2017
,
Apr 6 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
,
Oct 23
The recent flakes (as of yesterday) are because of issue 897925 . Other than that it has been passing 100% recently FWICT. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by guidou@chromium.org
, Mar 10 2017Owner: jaekyun@chromium.org
Status: Assigned (was: Untriaged)