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

Issue 681161 link

Starred by 1 user
Status: Fixed
Owner:
dpranke@chromium.org
Closed: Jan 2017
Cc:
█ tsniatow...@opera.com
sdefresne@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

"analyze" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jan 13 2017 
"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 3 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 674213 .

Comment 1 by dpranke@chromium.org, Jan 13 2017

Cc: tsniatow...@opera.com sdefresne@chromium.org
Components: Build
Labels: Build-Tools-GN
Owner: brettw@chromium.org
Status: Assigned (was: Untriaged)
The errors from this look very suspicious:

http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_rel_ng/builds/346227
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/370398
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds/135250

are all reporting "invalid targets".

analyze was never flaky before. Between this and  bug 680268 , I think the latest GN roll has probably introduced some regressions.

Comment 2 by dpranke@chromium.org, Jan 13 2017

Labels: OS-All

Comment 3 by dpranke@chromium.org, Jan 14 2017 

It looks like the latest GN does not have the fix for  bug 674213 , so I'm going to try rolling forward and see what happens.

Comment 4 by dpranke@chromium.org, Jan 15 2017

Owner: dpranke@chromium.org
Status: Fixed (was: Assigned)
This is hopefully fixed by 

https://codereview.chromium.org/2635713002
https://chromium.googlesource.com/chromium/src/+/2592262cc9dc8ea6cbe00a69a9b25b37970dae13
Cr-Commit-Position: refs/heads/master@{#443805}
►

Sign in to add a comment