GN analyze not detecting that targets need to be compiled when an action's script changes |
|||||
Issue descriptionSee parent bug. A change only touched CodeGeneratorInstrumentation.py and no C++ source files. The GN bots skipped compiles/tests because of analyze. But the GYP bot seems to have noticed this correctly. Here's the change that triggered this: https://codereview.chromium.org/2139443002 This chromeos GN bot for example skipped building any targets: https://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-generic_chromium_compile_only_ng/builds/165438 However this chromeos GYP build seemed to have noticed that targets were affected: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/199057
,
Jul 13 2016
i.e., `refs` should look at `script`s as well.
,
Jul 17 2016
,
Jul 19 2016
,
Jul 19 2016
This isn't a Blink>Infra issue; changing the component to Build instead.
,
Jul 19 2016
,
Jul 19 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/aca08753b705ef13f334c9f0aee6d44c217e4ad6 commit aca08753b705ef13f334c9f0aee6d44c217e4ad6 Author: dpranke <dpranke@chromium.org> Date: Tue Jul 19 20:23:39 2016 Make `gn refs` look at script files. Currently, `gn refs` would not look at the script files listed in action() and action_foreach() targets, so, for example `gn refs out/Default //tools/grit/grit.py` would return no references. This (a) is obviously incorrect, and (b) meant that analyze would not handle this case correctly and compiles would get skipped as a result. R=brettw@chromium.org BUG= 627667 Review-Url: https://codereview.chromium.org/2164773002 Cr-Commit-Position: refs/heads/master@{#406368} [modify] https://crrev.com/aca08753b705ef13f334c9f0aee6d44c217e4ad6/tools/gn/command_refs.cc
,
Jul 20 2016
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dpranke@chromium.org
, Jul 13 2016