aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar Googler <noreply@google.com>2018-04-03 12:13:44 -0700
committerGravatar Copybara-Service <copybara-piper@google.com>2018-04-03 12:15:44 -0700
commit077c6d68fe9671835a404cf4bbfea525acf3f2da (patch)
tree0db30f62c9a1ba657e3ddf3bba3b5465beee3dde
parentc83d8758ef30ecdd724b099874b922dddf6494ef (diff)
Update docs for the --test_timeout value.
RELNOTES: None. PiperOrigin-RevId: 191480343
-rw-r--r--src/main/java/com/google/devtools/build/docgen/templates/attributes/test/timeout.html6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/main/java/com/google/devtools/build/docgen/templates/attributes/test/timeout.html b/src/main/java/com/google/devtools/build/docgen/templates/attributes/test/timeout.html
index d11d0a4bc6..f676ce243a 100644
--- a/src/main/java/com/google/devtools/build/docgen/templates/attributes/test/timeout.html
+++ b/src/main/java/com/google/devtools/build/docgen/templates/attributes/test/timeout.html
@@ -36,3 +36,9 @@ correspond to the following time periods:
<td>60 minutes</td>
</tr>
</table>
+
+For times other than the above, the test timeout can be overridden with the
+<code>--test_timeout</code> bazel flag, e.g. for manually running under
+conditions which are known to be slow. The <code>--test_timeout</code> values
+are in seconds. For example <code>--test_timeout=120</code> will set the test
+timeout to two minutes.