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

Issue 592808 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 592715



Sign in to add a comment

Collect failed compile "target" from ninja on Waterfall.

Project Member Reported by st...@chromium.org, Mar 8 2016

Issue description

(A "target" here is a node in ninja's build graph.)

After next ninja release (version 1.7), ninja will print the output nodes of the failed edges. An edge is an execution task in ninja.

We wanted to collect such info to:
1. Speed up culprit-finding by minimizing the number of tasks to be executed by ninja during rerun of compile.
2. Confirm whether a re-run of compile fails for the same reason as those on the Waterfall.
3. De-duplicate same compile failures across different build configurations on the Waterfall. (This could reduce the number of culprit-finding try-jobs for the same compile failures on different bots.)
 

Comment 1 by st...@chromium.org, Mar 8 2016

Cc: st...@chromium.org
 Issue 584468  has been merged into this issue.
Project Member

Comment 2 by bugdroid1@chromium.org, Mar 15 2016

Comment 3 by st...@chromium.org, Mar 15 2016

Blocking: 592715

Comment 4 by st...@chromium.org, Mar 22 2016

The CL to collect failed "target"s directly from ninja is https://codereview.chromium.org/1766873002/, but might need some tweaking after release of ninja 1.7

Comment 5 by st...@chromium.org, Apr 22 2016

Components: Tools>Test>FindIt

Comment 6 by st...@chromium.org, Apr 25 2017

Status: Verified (was: Assigned)
Mark as fixed because the recipe change to collect failed targets on the recipe side seems not preferred by nico.

Sign in to add a comment