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
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -341,9 +341,13 @@ System Partition Configuration
341
341
:default: ``{}``
342
342
343
343
Processor information for this partition stored in a `processor info object <#processor-info>`__.
344
+
If not set, ReFrame will try to auto-detect this information (see :ref:`proc-autodetection` for more information).
344
345
345
346
.. versionadded:: 3.5.0
346
347
348
+
.. versionchanged:: 3.7.0
349
+
ReFrame is now able to detect the processor information automatically.
350
+
347
351
348
352
.. js:attribute:: .systems[].partitions[].devices
349
353
@@ -1201,6 +1205,28 @@ General Configuration
1201
1205
The command-line option sets the configuration option to ``false``.
1202
1206
1203
1207
1208
+
.. js:attribute:: .general[].remote_detect
1209
+
1210
+
:required: No
1211
+
:default: ``false``
1212
+
1213
+
Try to auto-detect processor information of remote partitions as well.
1214
+
This may slow down the initialization of the framework, since it involves submitting auto-detection jobs to the remote partitions.
1215
+
For more information on how ReFrame auto-detects processor information, you may refer to :ref:`proc-autodetection`.
1216
+
1217
+
.. versionadded:: 3.7.0
1218
+
1219
+
1220
+
.. js:attribute:: .general[].remote_workdir
1221
+
1222
+
:required: No
1223
+
:default: ``"."``
1224
+
1225
+
The temporary directory prefix that will be used to create a fresh ReFrame clone, in order to auto-detect the processor information of a remote partition.
ReFrame is able to detect the processor topology of both local and remote partitions automatically.
417
+
The processor and device information are made available to the tests through the corresponding attributes of the :attr:`~reframe.core.pipeline.RegressionTest.current_partition` allowing a test to modify its behavior accordingly.
418
+
Currently, ReFrame supports auto-detection of the local or remote processor information only.
419
+
It does not support auto-detection of devices, in which cases users should explicitly specify this information using the |devices|_ configuration option.
420
+
The processor information auto-detection works as follows:
421
+
422
+
#. If the |processor|_ configuration is option is defined, then no auto-detection is attempted.
423
+
424
+
#. If the |processor|_ configuration option is not defined, ReFrame will look for a processor configuration metadata file in ``{configdir}/_meta/{system}-{part}/processor.json`` or in ``~/.reframe/topology/{system}-{part}/processor.json`` in case of the builtin configuration file.
425
+
If the file is found, the topology information is loaded from there.
426
+
These files are generated automatically by ReFrame from previous runs.
427
+
428
+
#. If the corresponding metadata files are not found, the processor information will be auto-detected.
429
+
If the system partition is local (i.e., ``local`` scheduler + ``local`` launcher), the processor information is auto-detected unconditionally and stored in the corresponding metadata file for this partition.
430
+
If the partition is remote, ReFrame will not try to auto-detect it unless the :envvar:`RFM_REMOTE_DETECT` or the |detect_remote_system_topology|_ configuration option is set.
431
+
In that case, the steps to auto-detect the remote processor information are the following:
432
+
433
+
a. ReFrame creates a fresh clone of itself in a temporary directory created under ``.`` by default.
434
+
This temporary directory prefix can be changed by setting the :envvar:`RFM_REMOTE_WORKDIR` environment variable.
435
+
b. ReFrame changes to that directory and launches a job that will first bootstrap the fresh clone and then run that clone with ``{launcher} ./bin/reframe --detect-host-topology=topo.json``.
436
+
The :option:`--detect-host-topology` option causes ReFrame to detect the topology of the current host,
437
+
which in this case would be the remote compute nodes.
438
+
439
+
In case of errors during auto-detection, ReFrame will simply issue a warning and continue.
The temporary directory prefix that will be used to create a fresh ReFrame clone, in order to auto-detect the processor information of a remote partition.
0 commit comments