Skip to content

Commit ce0f240

Browse files
authored
Merge pull request #7176 from os-autoinst-bot/gh-pages-260324044456
Update documentation to commit ea002ef
2 parents 2373a7b + 331ecc4 commit ce0f240

3 files changed

Lines changed: 9 additions & 4 deletions

File tree

docs/api/testapi.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2162,7 +2162,7 @@ <h5 id="_get_serialdev_set_serialdev">get_serialdev, set_serialdev</h5>
21622162
</div>
21632163
<div id="footer">
21642164
<div id="footer-text">
2165-
Last updated 2026-03-21 04:48:03 UTC
2165+
Last updated 2026-03-24 04:45:27 UTC
21662166
</div>
21672167
</div>
21682168
</body>

docs/current.pdf

2.86 KB
Binary file not shown.

docs/index.html

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7670,6 +7670,10 @@ <h4 id="_test_flags"><a class="anchor" href="#_test_flags"></a><a class="link" h
76707670
fails. The overall state is set to <code>failed</code>.</p>
76717671
</li>
76727672
<li>
7673+
<p><strong>always_run</strong>: When set to <code>1</code> the test module is executed even if a previous
7674+
test module failed with <code>fatal</code>.</p>
7675+
</li>
7676+
<li>
76737677
<p><strong>ignore_failure</strong>: When set to <code>1</code> and the test module fails, it will not
76747678
affect the overall result at all.</p>
76757679
</li>
@@ -8137,7 +8141,8 @@ <h3 id="_capturing_kernel_exceptions_andor_any_other_exceptions_from_the_serial_
81378141
they match the serial output which is done after the test is executed. In case
81388142
it does not make sense to continue the test run even if the current test module
81398143
does not have the fatal flag, use <code>fatal</code> as serial failure type, so all
8140-
subsequent test modules will not be executed if such failure was detected.</p>
8144+
subsequent test modules (unless marked with <code>always_run</code>) will not be
8145+
executed if such failure was detected.</p>
81418146
</div>
81428147
<div class="paragraph">
81438148
<p>To use this functionality the test developer needs to define the patterns to
@@ -10130,7 +10135,7 @@ <h4 id="_snapshot_modes"><a class="anchor" href="#_snapshot_modes"></a><a class=
1013010135
<p>In both modes there is no need to modify tests (i.e. adding <code>milestone</code> test
1013110136
flag as the behaviour is implied). In the latter mode every test module is also
1013210137
considered <code>fatal</code>. This means the job is aborted after the first failed test
10133-
module.</p>
10138+
module (unless subsequent modules are marked with <code>always_run</code>).</p>
1013410139
</div>
1013510140
</div>
1013610141
<div class="sect3">
@@ -15215,7 +15220,7 @@ <h2 id="_contact_information"><a class="anchor" href="#_contact_information"></a
1521515220
</div>
1521615221
<div id="footer">
1521715222
<div id="footer-text">
15218-
Last updated 2026-03-21 04:47:14 UTC
15223+
Last updated 2026-03-24 04:44:39 UTC
1521915224
</div>
1522015225
</div>
1522115226
</body>

0 commit comments

Comments
 (0)