"ResourceFetcherTests.ResourceFetcherPost" is flaky |
||||||
Issue description"ResourceFetcherTests.ResourceFetcherPost" 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 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMwsSBUZsYWtlIihSZXNvdXJjZUZldGNoZXJUZXN0cy5SZXNvdXJjZUZldGNoZXJQb3N0DA. 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
yoshiki@: Can you take a look or try to find a better owner?
,
Mar 13 2017
Oka-san, could you triage?
,
Mar 13 2017
This test doesn't look related to Files app. https://cs.chromium.org/chromium/src/content/renderer/resource_fetcher_browsertest.cc?q=ResourceFetcherTests+ResourceFetcherPost&dr=CSs&l=348 mmenke@ could you triage?
,
Mar 13 2017
Oka: Are you assigning this to me because you think it's related to a CL I lande, or because you think I know the code? This is testing renderer-side code (Though, admittedly, browser tests run browser-side code as well), which I don't know at all.
,
Mar 14 2017
Hasn't failed since the 9th, closing the bug. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by guidou@chromium.org
, Mar 10 2017