New issue
Advanced search Search tips

Issue 618767 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 725672
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"android_webview_unittests (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 9 2016

Issue description

"android_webview_unittests (with patch)" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMQsSBUZsYWtlIiZhbmRyb2lkX3dlYnZpZXdfdW5pdHRlc3RzICh3aXRoIHBhdGNoKQw.



This flaky test/step was previously tracked in  issue 606881 .
 

Comment 1 by scheib@chromium.org, Jun 10 2016

Cc: bpastene@chromium.org
Labels: -Sheriff-Chromium
All appeared in 3 runs at about the same time in similar ways on linux_android_rel_ng.
 crbug.com/618904 
 crbug.com/618897 
 crbug.com/618893 
 crbug.com/618767 
 crbug.com/618250 
Project Member

Comment 2 by chromium...@appspot.gserviceaccount.com, May 25 2017

Labels: Sheriff-Chromium
Detected 4 new flakes for test/step "android_webview_unittests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMQsSBUZsYWtlIiZhbmRyb2lkX3dlYnZpZXdfdW5pdHRlc3RzICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).
Mergedinto: 725672
Status: Duplicate (was: Untriaged)
All this seems to be an issue of lacking capacity.  bug 725672  should fix that

Sign in to add a comment