"SitePerProcessBrowserTest.KillingRendererClearsDescendantProxies" is flaky |
||||
Issue description"SitePerProcessBrowserTest.KillingRendererClearsDescendantProxies" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySwsSBUZsYWtlIkBTaXRlUGVyUHJvY2Vzc0Jyb3dzZXJUZXN0LktpbGxpbmdSZW5kZXJlckNsZWFyc0Rlc2NlbmRhbnRQcm94aWVzDA. 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
,
Feb 17 2017
All the failures happened a day ago and none today. Might be a wontfix.
,
Feb 17 2017
cc-ing kenrb@chromium.org who better knows mouse leave/enter (which is in the stack trace of crash).
,
Apr 13 2017
There were no flakes since Feb 22, so I'll close this as WontFix. Let's reopen if this reoccurs. |
||||
►
Sign in to add a comment |
||||
Comment 1 by cfroussios@chromium.org
, Feb 17 2017Owner: davidsac@chromium.org