From 085b4cc28a8dd4fbab5badc1961a7710d78cd438 Mon Sep 17 00:00:00 2001 From: Googler Date: Tue, 7 Nov 2017 19:16:51 +0100 Subject: RELNOTES: Document interaction between test_suite and target exclusions Now with more accuracy. PiperOrigin-RevId: 174873635 --- .../google/devtools/build/lib/runtime/commands/target-syntax.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'src/main/java/com/google/devtools/build/lib/runtime') diff --git a/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt b/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt index df0089bf8b..e334d39f67 100644 --- a/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt +++ b/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt @@ -74,4 +74,12 @@ Subtractive patterns: build the former %{product} has to build the latter too. As usual, the '--' is required to prevent '-f' from being interpreted as an option. + When running the test command, test suite expansion is applied to each target + pattern in sequence as the set of targets is evaluated. This means that + individual tests from a test suite can be excluded by a later target pattern. + It also means that an exclusion target pattern which matches a test suite will + exclude all tests which that test suite references. (Targets that would be + matched by the list of target patterns without any test suite expansion are + also built unless --build_tests_only is set.) + %{options} -- cgit v1.2.3