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

Issue 604954 link

Starred by 0 users
Status: Fixed
Owner:
mar...@chromium.org
Closed: Jun 2016
Cc:
bpastene@chromium.org
█ stip@chromium.org
no...@chromium.org
█ borenet@chromium.org
rmis...@chromium.org
mar...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"[trigger] (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Apr 20 2016 
"[trigger] (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 10 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIQsSBUZsYWtlIhZbdHJpZ2dlcl0gKHdpdGggcGF0Y2gpDA.

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 kjellander@chromium.org, Apr 21 2016

Labels: -Sheriff-Chromium
Owner: mar...@chromium.org
Status: Assigned (was: Untriaged)
maruel: some trigger tasks seems to have failed. 
Example: https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/56539

Sending the report ... done.
Report URL: https://chromium-swarm.appspot.com/restricted/ereporter2/errors/5182571479564288
Failed to trigger task content_browsertests (with patch)/Android/29605fe598/linux_android_rel_ng/56539
step returned non-zero exit code: 1

Comment 2 by mar...@chromium.org, Apr 21 2016

Cc: bpastene@chromium.org no...@chromium.org rmis...@chromium.org borenet@chromium.org
The dot had more implication than expected. I'll start adding dot as a valid character in the regexp. Nodir will have to modify the copy of the regexp in buildbucket to allow it there too.

Comment 3 by mar...@chromium.org, Apr 21 2016

Cc: stip@chromium.org
Components: -Tests>Flaky
Labels: Infra-Swarming Infra-Android

Comment 5 by aga...@chromium.org, Apr 26 2016

Components: Infra>Platform>Swarming
Labels: -Infra-Swarming

Comment 6 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>Android
Labels: -Infra-Android

Comment 7 by stip@chromium.org, Apr 28 2016 

Can we close this?
Project Member

Comment 8 by chromium...@appspot.gserviceaccount.com, May 25 2016 

Detected 8 new flakes for test/step "[trigger] (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIQsSBUZsYWtlIhZbdHJpZ2dlcl0gKHdpdGggcGF0Y2gpDA. 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).
Project Member

Comment 9 by chromium...@appspot.gserviceaccount.com, Jun 2 2016 

Detected 35 new flakes for test/step "[trigger] (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIQsSBUZsYWtlIhZbdHJpZ2dlcl0gKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app.

Comment 10 by bpastene@chromium.org, Jun 2 2016

Status: Fixed (was: Assigned)
Original issue is fixed.

Looks all recent flakes are fallout from yesterday's swarming outage.
►

Sign in to add a comment