"SupervisedUserURLFilterTest.Inactive" is flaky |
||||
Issue description"SupervisedUserURLFilterTest.Inactive" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRTdXBlcnZpc2VkVXNlclVSTEZpbHRlclRlc3QuSW5hY3RpdmUM. 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
,
Apr 26 2017
Issue 715472 has been merged into this issue.
,
Apr 26 2017
Issue 715470 has been merged into this issue.
,
Apr 26 2017
Issue 715490 has been merged into this issue.
,
Apr 26 2017
,
Apr 27 2017
That looks like gab@ area, I have no clue.
,
May 2 2017
Looks like there haven't been recent flakes (and the test doesn't appear to have been disabled). It was likely a case of a test using the scheduler while it wasn't initialized. Francois added TaskScheduler initialization in a LOT more places recently so that likely fixed it. |
||||
►
Sign in to add a comment |
||||
Comment 1 by zmin@chromium.org
, Apr 26 2017Status: Assigned (was: Untriaged)