New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 726239 link

Starred by 1 user
Status: Duplicate
Merged: issue 725672
Owner: ----
Closed: May 2017
Cc:
█ mgiuca@chromium.org
█ bryanhenry@google.com
chanli@chromium.org
seanmccullough@chromium.org
liaoyuke@chromium.org
chrome-trooper-bugs@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

linux_android_rel_ng flaky exception: "shard #0 expired, not enough capacity"

Project Member Reported by chromium...@appspot.gserviceaccount.com, May 25 2017 
"sandbox_linux_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 5 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRzYW5kYm94X2xpbnV4X3VuaXR0ZXN0cyAod2l0aCBwYXRjaCkM.

The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4.

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

Comment 2 by mgiuca@chromium.org, May 25 2017 

 Issue 726217  has been merged into this issue.

Comment 3 by mgiuca@chromium.org, May 26 2017

Cc: mgiuca@chromium.org
Labels: OS-Android
Summary: linux_android_rel_ng flaky exception: "shard #0 expired, not enough capacity" (was: "sandbox_linux_unittests (with patch)" is flaky)
This is a recurring theme on the Sheriff tracker. I'm about to dupe a bunch more issues into this. Renaming to a more generic name.

Comment 4 by mgiuca@chromium.org, May 26 2017 

 Issue 725797  has been merged into this issue.

Comment 5 by mgiuca@chromium.org, May 26 2017 

 Issue 726585  has been merged into this issue.

Comment 6 by mgiuca@chromium.org, May 26 2017 

 Issue 726592  has been merged into this issue.

Comment 7 by mgiuca@chromium.org, May 26 2017 

 Issue 726593  has been merged into this issue.

Comment 8 by mgiuca@chromium.org, May 26 2017 

 Issue 726280  has been merged into this issue.

Comment 9 by mgiuca@chromium.org, May 26 2017 

 Issue 726605  has been merged into this issue.

Comment 10 by bryanhenry@google.com, May 26 2017

Cc: bryanhenry@google.com
I saw two CQ failures in a row on https://chromium-review.googlesource.com/c/516243/ earlier today, so it took ~6 hours to submit.

Comment 11 by jbudorick@chromium.org, May 26 2017

Mergedinto: 725672
Status: Duplicate (was: Untriaged)
We're in the process of rolling out additional capacity for this bot.
►

Sign in to add a comment