You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/manpage.rst
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -361,19 +361,23 @@ When allocating nodes automatically, ReFrame will take into account all node lim
361
361
Nodes from this pool are allocated according to different policies.
362
362
If no node can be selected, the test will be marked as a failure with an appropriate message.
363
363
364
-
.. option:: --flex-alloc-nodes[=POLICY]
364
+
.. option:: --flex-alloc-nodes=POLICY
365
365
366
366
Set the flexible node allocation policy.
367
367
Available values are the following:
368
368
369
369
- ``all``: Flexible tests will be assigned as many tasks as needed in order to span over *all* the nodes of the node pool.
370
-
- ``idle``: Flexible tests will be assigned as many tasks as needed in order to span over the *idle* nodes of the node pool.
370
+
- ``STATE``: Flexible tests will be assigned as many tasks as needed in order to span over the nodes that are currently in state ``STATE``.
371
371
Querying of the node state and submission of the test job are two separate steps not executed atomically.
372
-
It is therefore possible that the number of tasks assigned does not correspond to the actual idle nodes.
372
+
It is therefore possible that the number of tasks assigned does not correspond to the actual nodes in the given state.
373
373
374
-
This is the default policy.
374
+
If this option is not specified, the default allocation policy for flexible tests is 'idle'.
375
375
- Any positive integer: Flexible tests will be assigned as many tasks as needed in order to span over the specified number of nodes from the node pool.
376
376
377
+
.. versionchanged:: 3.1
378
+
It is now possible to pass an arbitrary node state as a flexible node allocation parameter.
0 commit comments