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

Issue 599355 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"ensure" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Mar 31 2016

Issue description

"ensure" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEQsSBUZsYWtlIgZlbnN1cmUM.

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
 

Comment 1 by jochen@chromium.org, Mar 31 2016

Labels: -Sheriff-Chromium
Owner: iannucci@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 2 by chromium...@appspot.gserviceaccount.com, Apr 1 2016

Labels: Sheriff-Chromium
Detected 6 new flakes for test/step "ensure". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEQsSBUZsYWtlIgZlbnN1cmUM. 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).
Status: WontFix (was: Assigned)
These all look like the crappy javascript downloader in depot_tools halted forever during the rollout (googlestorage got slightly over quota for that object today). I've verified that all of those machines succeeded on this step on a subsequent build (the ensure tools step is sticky, so it only needs to pass once to be up to date).

If we see this pop up more, we should reopen, but I'm pretty confident that this was a small transient.

Sign in to add a comment