From edeeb780e554b4c49d5a4ee26c7aa376284abdca Mon Sep 17 00:00:00 2001 From: Googler Date: Sat, 4 Nov 2017 01:24:46 +0100 Subject: Automated rollback of commit 0dffc49f528c4c6e641221060e41aa6896310bdf. *** Reason for rollback *** This doesn't seem to be correct. I was confused by an example where a target is excluded from being run, but still built. *** Original change description *** RELNOTES: Document interaction between test_suite and target exclusions PiperOrigin-RevId: 174536378 --- .../com/google/devtools/build/lib/runtime/commands/target-syntax.txt | 5 ----- 1 file changed, 5 deletions(-) (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 f67759836b..df0089bf8b 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,9 +74,4 @@ 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. - Note that test suite expansion is performed only after the full list of - target patterns is evaluated. That means if an exclusion matches a test_suite - target, only the test_suite itself is excluded, not all of the individual test - targets. - %{options} -- cgit v1.2.3