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

Issue 684060 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"analyze" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jan 23 2017

Issue description

"analyze" 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 not infrastructure-related (e.g. flaky test), please add Sheriff-Chromium label and change issue status to Untriaged. When done, please remove the issue from Trooper Bug Queue by removing the Infra-Troopers label.

We have detected 7 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEgsSBUZsYWtlIgdhbmFseXplDA.



This flaky test/step was previously tracked in  issue 681161 .
 
Cc: sergeybe...@chromium.org aber...@chromium.org jbudorick@chromium.org phajdan.jr@chromium.org
Status: WontFix (was: Untriaged)
This was caused by a bad change landing on the waterfall in 

https://codereview.chromium.org/2627093009

it was reverted in

https://codereview.chromium.org/2648383002

It looks like the problematic CL was missing an entry in gn_isolate_map.pyl, which caused analyze to fail. 

However, because we changed //testing/buildbot/*.json, the recipe's whitelist of "changes we can't analyze" (//testing/buildbot/trybot_analyze_config.json) matched, and so we skipped analyze and didn't detect the bug.

I've filed  crbug.com/684226  to address this.

Also, note that checking to see if we had this failure on the waterfall builders is useless, since we don't run analyze on the waterfall builders.


Sign in to add a comment