Failure tokens¶
The prolog exits 0 in every row. A chained prolog’s non-zero status is the exception: it is returned as-is and the guard does not restore modules.
Situation |
|
Output |
|---|---|---|
|
unset |
Silent. EESSI is not loaded. |
|
unset |
Silent opt-out. |
|
unset |
Silent. Detection is pinned. |
|
depends on the CPU |
Accelerator is not compared. |
Same CPU and accelerator |
unset |
Silent. No exports. |
No software directory for any candidate |
|
One |
archdetect missing, non-zero, empty, or unsafe |
|
One |
|
unset on success |
That candidate is skipped. The next installed candidate is loaded, and |
A loaded name fails the grammar |
|
Restore does not start. |
The list has no single |
|
Restore does not start. |
|
|
Restore does not start. |
A module has no build for this target |
|
One |
A changed value cannot be a prolog line |
|
No partial delta. |
Unexpected exception |
unchanged, plus a skip line |
One |
Deadline exhausted |
|
The waited-on process group is killed. The result is not cached. |
|
|
The same kill. The result is not cached. |
|
unchanged |
Skip and match reasons go to stderr. |
<was> is EESSI_SOFTWARE_SUBDIR, or <cpu> <accel> / <cpu> no accel once both sides are known. <subdir> on the deadline rows is EESSI_SOFTWARE_SUBDIR alone.
How to act on a line is Correct a guard message.