aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar philwo <philwo@google.com>2017-05-04 12:47:19 +0200
committerGravatar Damien Martin-Guillerez <dmarting@google.com>2017-05-04 13:14:37 +0200
commit8bd4312fb8e738fe0cf7bd5edb5152db6325c6ad (patch)
tree0920ec92c2b752d400d17fa302d1cd90b184c622 /site
parentc58ba098526b748f9c73e6229cafd74748205aa1 (diff)
Improve docs regarding the CPU core reservation feature for tests.
PiperOrigin-RevId: 155063811
Diffstat (limited to 'site')
-rw-r--r--site/versions/master/docs/test-encyclopedia.html5
1 files changed, 4 insertions, 1 deletions
diff --git a/site/versions/master/docs/test-encyclopedia.html b/site/versions/master/docs/test-encyclopedia.html
index 6a9b0e85e9..76e326283b 100644
--- a/site/versions/master/docs/test-encyclopedia.html
+++ b/site/versions/master/docs/test-encyclopedia.html
@@ -334,7 +334,10 @@ resolve.</p>
<p>Tests are granted at least one CPU core. Others may be available but this
is not guaranteed. Other performance aspects of this core are not specified.
You can increase the reservation to a higher number of CPU cores by adding the
-tag "cpu:n" (where n is a positive number) to a test rule.</p>
+tag "cpu:n" (where n is a positive number) to a test rule. If a machine has
+less total CPU cores than requested, Bazel will still run the test. If a test
+uses sharding, each individual shard will reserve the number of CPU cores
+specified here.</p>
<p>Tests may create subprocesses, but not process groups or sessions.</p>