Issue metadata
Sign in to add a comment
|
"ChromeRenderProcessHostTest.ProcessOverflow" is flaky |
||||||||||||||||||||||
Issue description"ChromeRenderProcessHostTest.ProcessOverflow" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyNgsSBUZsYWtlIitDaHJvbWVSZW5kZXJQcm9jZXNzSG9zdFRlc3QuUHJvY2Vzc092ZXJmbG93DA. 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 25 2016
Issue 606118 has been merged into this issue.
,
Apr 25 2016
Issue 606095 has been merged into this issue.
,
Apr 25 2016
https://codereview.chromium.org/1892033003 is not related to this problem. Code in base/task_scheduler is not used anywhere for now.
,
Apr 25 2016
Also flaky: ChromeRenderProcessHostTest.ProcessPerTab ChromeRenderProcessHostTestWithCommandLine.ProcessOverflowCommandLine (see merged bugs: bug 606118 and bug 606095 )
,
Apr 25 2016
Huh, turns out those have been flaky for a while, and we have an old bug for it. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by treib@chromium.org
, Apr 25 2016Owner: fdoray@chromium.org
Status: Assigned (was: Untriaged)