https-github-com-bit
diff --git a/‎test/README.testsuite‎
Lines changed: 23 additions & 0 deletions b/‎test/README.testsuite‎
Lines changed: 23 additions & 0 deletions
diff --git a/‎test/TEST-24-UNIT-TESTS/blacklist-ubuntu-ci-ppc64el‎ b/‎test/TEST-24-UNIT-TESTS/blacklist-ubuntu-ci-ppc64el‎
diff --git a/‎test/TEST-25-IMPORT/blacklist-ubuntu-ci‎ b/‎test/TEST-25-IMPORT/blacklist-ubuntu-ci‎
diff --git a/‎test/TEST-30-ONCLOCKCHANGE/blacklist-ubuntu-ci-i386‎ b/‎test/TEST-30-ONCLOCKCHANGE/blacklist-ubuntu-ci-i386‎
diff --git a/‎test/TEST-36-NUMAPOLICY/blacklist-ubuntu-ci-s390x‎ b/‎test/TEST-36-NUMAPOLICY/blacklist-ubuntu-ci-s390x‎
diff --git a/‎test/TEST-40-EXEC-COMMAND-EX/blacklist-ubuntu-ci-arm64‎ b/‎test/TEST-40-EXEC-COMMAND-EX/blacklist-ubuntu-ci-arm64‎
@@ -97,3 +97,26 @@ kernel command line parameter with $KERNEL_APPEND and then log in as root.
 $ sudo make -C test/TEST-01-BASIC KERNEL_APPEND="systemd.unit=multi-user.target" run
 
 Root password is empty.
+
+Ubuntu CI
+=========
+
+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
+'Ubuntu CI'.  Part of that testing is to run all these tests.  Sometimes these
+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
+named 'blacklist-ubuntu-ci', for example to prevent the TEST-01-BASIC test from
+running in the 'autopkgtest' runs, create the file
+'TEST-01-BASIC/blacklist-ubuntu-ci'.
+
+The tests may be disabled only for specific archs, by creating a blacklist file
+with the arch name at the end, e.g.
+'TEST-01-BASIC/blacklist-ubuntu-ci-arm64' to disable the TEST-01-BASIC test
+only on test runs for the 'arm64' architecture.
+
+Note the arch naming is not from 'uname -m', it is Debian arch names:
+https://wiki.debian.org/ArchitectureSpecificsMemo
+
+For PRs that fix a currently blacklisted test, the PR should include removal
+of the blacklist file.