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/config_reference.rst
+44-3Lines changed: 44 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -438,12 +438,14 @@ System Partition Configuration
438
438
439
439
Ignore the ``ReqNodeNotAvail`` Slurm state.
440
440
441
-
If a job associated to a test is in pending state with the Slurm reason ``ReqNodeNotAvail`` and a list of unavailable nodes is also specified, ReFrame will check the status of the nodes and, if all of them are indeed down, it will cancel the job.
442
-
Sometimes, however, when Slurm's backfill algorithm takes too long to compute, Slurm will set the pending reason to ``ReqNodeNotAvail`` and mark all system nodes as unavailable, causing ReFrame to kill the job.
441
+
If a job associated to a test is in pending state with the Slurm reason ``ReqNodeNotAvail``, ReFrame will cancel the job.
442
+
Sometimes, however, when Slurm's backfill algorithm takes too long to compute, Slurm will set the pending reason to ``ReqNodeNotAvail`` and mark all system nodes as unavailable, causing ReFrame to its jobs.
443
443
In such cases, you may set this parameter to :obj:`True` to avoid this.
444
444
445
445
This option is relevant for the Slurm backends only.
Frequency of polling for the reason a Slurm job is pending.
520
+
521
+
When using the ``slurm`` backend, ReFrame needs to explicitly issue an ``squeue`` command to get the reason a job is pending, in order to cancel it if it is blocked indefinitely.
522
+
This option controls the frequency of this polling.
523
+
It is an integer number counting the number of job polling cycles before issuing the ``squeue`` command.
524
+
ReFrame will issue a single ``squeue`` command to query all pending jobs at once.
525
+
However, if your system is sensitive to Slurm RPC calls, you may consider increasing this value.
526
+
527
+
This option is relevant for the ``slurm`` backend only.
0 commit comments