Get Detailed Information from Ninja after compile failure |
|||||
Issue descriptionWhat steps will reproduce the problem? (1)Parse ninja stdout to get failed nodes (2)Parse ninja output of deps & graph tool to find original files that failed nodes depend on (3)Modify recipe to collect information after compile failure
,
Jul 12 2017
,
Jul 28 2017
,
Aug 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/4df95728c0f93f35524533569638745ababbfc20 commit 4df95728c0f93f35524533569638745ababbfc20 Author: Yichun Li <yichunli@google.com> Date: Wed Aug 02 19:24:28 2017 Get detailed information of compile failure api will call this wrapper: https://chromium-review.googlesource.com/c/585850/ Script reads stdout of ninja first, and parses it to get failed nodes. Then it runs deps/graph tool to find dependency file of failed nodes. Bug: 736405 Change-Id: I960b75439deda14a1261142353cd9545d283a655 Reviewed-on: https://chromium-review.googlesource.com/527494 Commit-Queue: Yichun Li <yichunli@google.com> Reviewed-by: Dirk Pranke <dpranke@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> [add] https://crrev.com/4df95728c0f93f35524533569638745ababbfc20/scripts/slave/recipe_modules/chromium/resources/ninja_wrapper.py [add] https://crrev.com/4df95728c0f93f35524533569638745ababbfc20/scripts/slave/recipe_modules/chromium/resources/ninja_wrapper_test.py
,
Aug 17 2017
The assigned owner "yichunli@google.com" is not able to receive e-mails, please re-triage. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 17 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by yichunli@google.com
, Jun 23 2017EstimatedDays: 7