Lines Matching refs:affected

20 and a list of targets to build and returns which targets are affected by
78 by only building and running the tests affected by the files in a patch, rather
84   everything that a patch affected on every patch. This does not
97   date due to a combination of files affected by a given patch, and files
98   affected for unrelated reasons. We want to rebuild and test only the
99   targets affected by the patch, so that we don't blame or punish the
105    we don't (the affected files of a patch).
120 3. We might also want to know when test targets are affected by data files
131    are affected by the patch. For example, if you have a meta target like
138    things are fast enough that we can afford to build everything affected by a
158 * `test_targets`: the list of ninja targets which, if affected by a patch,
172   dependendencies of the target are affected by the patch (i.e.,
216 build, or that there were no affected test targets as appropriate.
222 potentially affected by the files. One could try to indicate