|
@@ -1331,6 +1331,15 @@ the running machine. This allows CTest to internally keep track of which
|
|
|
resources are in use and which are free, scheduling tests in a way that
|
|
resources are in use and which are free, scheduling tests in a way that
|
|
|
prevents them from trying to claim resources that are not available.
|
|
prevents them from trying to claim resources that are not available.
|
|
|
|
|
|
|
|
|
|
+When the resource allocation feature is used, CTest will not oversubscribe
|
|
|
|
|
+resources. For example, if a resource has 8 slots, CTest will not run tests
|
|
|
|
|
+that collectively use more than 8 slots at a time. This has the effect of
|
|
|
|
|
+limiting how many tests can run at any given time, even if a high ``-j``
|
|
|
|
|
+argument is used, if those tests all use some slots from the same resource.
|
|
|
|
|
+In addition, it means that a single test that uses more of a resource than is
|
|
|
|
|
+available on a machine will not run at all (and will be reported as
|
|
|
|
|
+``Not Run``).
|
|
|
|
|
+
|
|
|
A common use case for this feature is for tests that require the use of a GPU.
|
|
A common use case for this feature is for tests that require the use of a GPU.
|
|
|
Multiple tests can simultaneously allocate memory from a GPU, but if too many
|
|
Multiple tests can simultaneously allocate memory from a GPU, but if too many
|
|
|
tests try to do this at once, some of them will fail to allocate, resulting in
|
|
tests try to do this at once, some of them will fail to allocate, resulting in
|
Kyle Edwards