Explicitly mention that 'manual' test targets are not matched by wildcard target patterns and are thus neither built nor tested by invocations like "blaze test //my/project/..."
--
MOS_MIGRATED_REVID=109251573
diff --git a/site/docs/bazel-user-manual.html b/site/docs/bazel-user-manual.html
index e712d56..6ee6052 100644
--- a/site/docs/bazel-user-manual.html
+++ b/site/docs/bazel-user-manual.html
@@ -520,9 +520,9 @@
building the former.
</p>
<p>
- Targets with <code>tags=["manual"]</code> will be ignored by all command line
- wildcards (..., :*, :all, etc). The only way to run such targets is to
- specify them explicitly on the command line.
+ Targets with <code>tags=["manual"]</code> will not be included in wildcard target patterns (...,
+ :*, :all, etc). You should specify such test targets with explicit target patterns on the command
+ line if you want Bazel to build/test them.
</p>
<h3 id='fetch'>Fetching external dependencies</h3>
diff --git a/site/docs/test-encyclopedia.html b/site/docs/test-encyclopedia.html
index d2501f1..f9e37e1 100644
--- a/site/docs/test-encyclopedia.html
+++ b/site/docs/test-encyclopedia.html
@@ -413,7 +413,7 @@
<tr>
<th><code>manual</code></th>
- <td>run test only if mentioned explicitly (not in a wildcard <code>:...</code>, <code>:*</code>, or <code>:all</code>)</td>
+ <td>don't include test target in wildcard target patterns like <code>:...</code>, <code>:*</code>, or <code>:all</code>)</td>
</tr>
<tr>
<th><code>medium</code></th>
diff --git a/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html b/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html
index 1937b33..e447335 100644
--- a/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html
+++ b/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html
@@ -48,18 +48,18 @@
</p>
<ul>
- <li><code>exclusive</code> keyword will force test to be run in the
+ <li><code>exclusive</code> keyword will force the test to be run in the
"exclusive" mode, ensuring that no other tests are running at the
same time. Such tests will be executed in serial fashion after all build
activity and non-exclusive tests have been completed. They will also always
run locally and thus without sandboxing.
</li>
- <li><code>manual</code> keyword will force test to be ignored by all command
- line wildcards (<code>...</code>, <code>:*</code>, <code>:all</code>, etc).
- It will also be ignored by the <code>test_suite</code> rules that do not
- mention this test explicitly. The only way
- to run such test is to specify it explicitly on the command line.
+ <li><code>manual</code> keyword will force the test target to not be included in target pattern
+ wildcards (<code>...</code>, <code>:*</code>, <code>:all</code>, etc); the test target will be
+ neither built nor run. It will also be ignored by the <code>test_suite</code> rules that do not
+ mention this test explicitly. The only way to build or run such a test is to specify it via an
+ explicit target pattern on the command line.
</li>
<li><code>external</code> keyword will force test to be unconditionally
diff --git a/tools/DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN b/tools/DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/tools/DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
