"org.chromium.android_webview.test.SafeBrowsingTest#testSafeBrowsingDontProceedNavigatesBackForMainFrame" is flaky |
||
Issue description"org.chromium.android_webview.test.SafeBrowsingTest#testSafeBrowsingDontProceedNavigatesBackForMainFrame" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNycgsSBUZsYWtlImdvcmcuY2hyb21pdW0uYW5kcm9pZF93ZWJ2aWV3LnRlc3QuU2FmZUJyb3dzaW5nVGVzdCN0ZXN0U2FmZUJyb3dzaW5nRG9udFByb2NlZWROYXZpZ2F0ZXNCYWNrRm9yTWFpbkZyYW1lDA. 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 26 2018
This seems to be a transient thing that has sorted itself out. Marking as WontFix, feel free to reopen if I'm missing something. |
||
►
Sign in to add a comment |
||
Comment 1 by boliu@chromium.org
, Mar 22 2018Labels: OS-Android
Owner: ntfschr@chromium.org
Status: Assigned (was: Untriaged)