While importing MariaDB 10.5 to Debian, I noticed that the test main.failed_auth_unixsocket fails on arch armhf and 386 (but arm64 or amd64) when the Debian autopkgtests run.
The test failure:
- i386 fail: https://ci.debian.net/data/autopkgtest/testing/i386/m/mariadb-10.5/7380360/log.gz
- armhf fail: https://ci.debian.net/data/autopkgtest/testing/armhf/m/mariadb-10.5/7380287/log.gz
- arm64 pass: https://ci.debian.net/data/autopkgtest/testing/arm64/m/mariadb-10.5/7380183/log.gz
- amd64 pass: https://ci.debian.net/data/autopkgtest/testing/amd64/m/mariadb-10.5/7380101/log.gz
This did not occur with previous MariaDB 10.3 in Debian.
Debian has this massive CI system where each upload of a package triggers CI testing of other packages that depend on it: https://ci.debian.net/status/
The tests mariadb-10.5 runs are in the path debian/tests.
In MariaDB 10.5 we run mtr from the debian/tests/upstream test to re-use the existing test suite. Why this seems to end differently on debci from when run in post-build armhf and i386 builds is unknown.
On Debian buildd post-build mtr passes on main.failed_auth_unixsocket fine, e.g.
Debci regressions are also automatically listed on the package tracker page and prevents unstable->testing migration:
Maybe the error code 1045 is just fine and test can be extended to accept it?
Or we can in Debian skip this one test in the autopkgtests to ignore it.