Compare commits

..

No commits in common. "825cba0d4327dcf88ed32aedfbe5851e2d65807c" and "73b432e7ef212bfad8a3652687621c87d26536b5" have entirely different histories.

7 changed files with 8 additions and 8 deletions

View File

@ -901,7 +901,7 @@
<programlisting>SuccessExitStatus=TEMPFAIL 250 SIGUSR1</programlisting> <programlisting>SuccessExitStatus=TEMPFAIL 250 SIGUSR1</programlisting>
<para>Exit status 75 (<constant>TEMPFAIL</constant>), 250, and the termination signal <para>Exit status 75 (<constant>TEMPFAIL</constant>), 250, and the termination signal
<constant>SIGUSR1</constant> are considered clean service terminations.</para> <constant>SIGKILL</constant> are considered clean service terminations.</para>
</example> </example>
<para>Note: <command>systemd-analyze exit-status</command> may be used to list exit statuses and <para>Note: <command>systemd-analyze exit-status</command> may be used to list exit statuses and

View File

@ -104,19 +104,19 @@ Ubuntu CI
New PR submitted to the project are run through regression tests, and one set New PR submitted to the project are run through regression tests, and one set
of those is the 'autopkgtest' runs for several different architectures, called of those is the 'autopkgtest' runs for several different architectures, called
'Ubuntu CI'. Part of that testing is to run all these tests. Sometimes these 'Ubuntu CI'. Part of that testing is to run all these tests. Sometimes these
tests are temporarily deny-listed from running in the 'autopkgtest' tests while tests are temporarily blacklisted from running in the 'autopkgtest' tests while
debugging a flaky test; that is done by creating a file in the test directory debugging a flaky test; that is done by creating a file in the test directory
named 'deny-list-ubuntu-ci', for example to prevent the TEST-01-BASIC test from named 'blacklist-ubuntu-ci', for example to prevent the TEST-01-BASIC test from
running in the 'autopkgtest' runs, create the file running in the 'autopkgtest' runs, create the file
'TEST-01-BASIC/deny-list-ubuntu-ci'. 'TEST-01-BASIC/blacklist-ubuntu-ci'.
The tests may be disabled only for specific archs, by creating a deny-list file The tests may be disabled only for specific archs, by creating a blacklist file
with the arch name at the end, e.g. with the arch name at the end, e.g.
'TEST-01-BASIC/deny-list-ubuntu-ci-arm64' to disable the TEST-01-BASIC test 'TEST-01-BASIC/blacklist-ubuntu-ci-arm64' to disable the TEST-01-BASIC test
only on test runs for the 'arm64' architecture. only on test runs for the 'arm64' architecture.
Note the arch naming is not from 'uname -m', it is Debian arch names: Note the arch naming is not from 'uname -m', it is Debian arch names:
https://wiki.debian.org/ArchitectureSpecificsMemo https://wiki.debian.org/ArchitectureSpecificsMemo
For PRs that fix a currently deny-listed test, the PR should include removal For PRs that fix a currently blacklisted test, the PR should include removal
of the deny-list file. of the blacklist file.