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

Issue 694975 link

Starred by 1 user
Status: WontFix
Owner:
█ smut@chromium.org
User never visited
Closed: Feb 2017
Cc:
mar...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

"devtools_eslint (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Feb 22 2017 
"devtools_eslint (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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyJwsSBUZsYWtlIhxkZXZ0b29sc19lc2xpbnQgKHdpdGggcGF0Y2gpDA.



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

Comment 1 by treib@chromium.org, Feb 23 2017

Cc: mar...@chromium.org
Labels: -Sheriff-Chromium OS-Linux
Owner: smut@chromium.org
Status: Assigned (was: Untriaged)
Adding some people from  bug 673723  which looks similar - tasks saying EXPIRED.
Any idea what's going on, or what do to about it? Looks like it only happened a few times yesterday, not today, so maybe it was some transient problem that's fixed itself in the meantime?

Anyway, taking out of the sheriff queue. If it happens again, the label will get re-added.

Comment 2 by treib@chromium.org, Feb 23 2017

Owner: s...@google.com

Comment 3 by s...@google.com, Feb 23 2017

Status: WontFix (was: Assigned)
"EXPIRED" means the Swarming server didn't have capacity to run the test in a reasonable amount of time.

The failures reported in this bug were launching 12.04 jobs on 2/21 and early 2/22 (before the Precise -> Trusty migration revert), which means they were running Precise jobs when we had migrated away from Precise, which should not have happened.

That said, since the Precise -> Trusty migration was reverted, we're back to 800 Precise VMs which should be enough to handle these tasks going forward.

Comment 4 by s...@google.com, Jun 23 2017

Owner: smut@chromium.org
►

Sign in to add a comment