Source: mariadb-10.5 Version: 1:10.5.5-3 Forwarded: https://jira.mariadb.org/browse/MDEV-23922 Tags: upstream, confirmed, help, ftbfs Severity: normal Justification: source does build, but tests don't run and binaries are unvalidated User: debian-...@lists.debian.org Usertags: m68k, 68k
As part of the MariaDB build there is a test suite that runs directly after the build has finished, and validates that the binaries run at least all the basic stuff as expected. On amd64 the build log looks like this: ********************* Source: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=amd64&ver=1%3A10.5.5-3&stamp=1602231226&raw=0 ********************* RULES.override_dh_auto_test dh_testdir # Skip unstable tests if such are defined for arch cp mysql-test/unstable-tests debian/mysql-test-unstable-tests.orig [ ! -f debian/unstable-tests.amd64 ] || cat debian/unstable-tests.amd64 >> mysql-test/unstable-tests # Run testsuite # Don't use --mem here as official Debian builders and most Docker systems don't have a large mem device available and # would fail with errors on lack of disk space. cd builddir/mysql-test && \ ./mtr --force --testcase-timeout=120 --suite-timeout=540 \ --retry=3 --parallel=4 --skip-rpl --suite=main \ --skip-test-list=unstable-tests Logging: /<<PKGBUILDDIR>>/mysql-test/mysql-test-run.pl --force --testcase-timeout=120 --suite-timeout=540 --retry=3 --parallel=4 --skip-rpl --suite=main --skip-test-list=unstable-tests vardir: /<<PKGBUILDDIR>>/builddir/mysql-test/var Removing old var directory... Creating var directory '/<<PKGBUILDDIR>>/builddir/mysql-test/var'... Checking supported features... MariaDB Version 10.5.5-MariaDB-3 - SSL connections supported Using suites: main Collecting tests... Installing system database... ********************* However, on m68k builds the log just says: ********************* Source: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=m68k&ver=1%3A10.5.5-3&stamp=1602368619&raw=0 ********************* RULES.override_dh_auto_test dh_testdir # Skip unstable tests if such are defined for arch cp mysql-test/unstable-tests debian/mysql-test-unstable-tests.orig [ ! -f debian/unstable-tests.m68k ] || cat debian/unstable-tests.m68k >> mysql-test/unstable-tests # Run testsuite make[1]: Leaving directory '/<<PKGBUILDDIR>>' create-stamp debian/debhelper-build-stamp dh_testroot -a -O--fail-missing dh_prep -a -O--fail-missing rm -f -- debian/libmariadb-dev.substvars debian/libmariadb-dev-compat.substvars debian/libmariadb3.substvars debian/libmariadbd19.substvars debian/libmariadbd-dev.substvars debian/mariadb-client-core-10.5.substvars debian/mariadb-client-10.5.substvars debian/mariadb-server-core-10.5.substvars debian/mariadb-server-10.5.substvars debian/mariadb-backup.substvars debian/mariadb-plugin-connect.substvars debian/mariadb-plugin-s3.substvars debian/mariadb-plugin-oqgraph.substvars debian/mariadb-plugin-spider.substvars debian/mariadb-plugin-gssapi-server.substvars debian/mariadb-plugin-gssapi-client.substvars debian/mariadb-plugin-cracklib-password-check.substvars debian/mariadb-test.substvars rm -fr -- debian/.debhelper/generated/libmariadb-dev/ debian/libmariadb-dev/ debian/tmp/ debian/.debhelper/generated/libmariadb-dev-compat/ debian/libmariadb-dev-compat/ debian/.debhelper/generated/libmariadb3/ debian/libmariadb3/ debian/.debhelper/generated/libmariadbd19/ debian/libmariadbd19/ debian/.debhelper/generated/libmariadbd-dev/ debian/libmariadbd-dev/ debian/.debhelper/generated/mariadb-client-core-10.5/ debian/mariadb-client-core-10.5/ debian/.debhelper/generated/mariadb-client-10.5/ debian/mariadb-client-10.5/ debian/.debhelper/generated/mariadb-server-core-10.5/ debian/mariadb-server-core-10.5/ debian/.debhelper/generated/mariadb-server-10.5/ debian/mariadb-server-10.5/ debian/.debhelper/generated/mariadb-backup/ debian/mariadb-backup/ debian/.debhelper/generated/mariadb-plugin-connect/ debian/mariadb-plugin-connect/ debian/.debhelper/generated/mariadb-plugin-s3/ debian/mariadb-plugin-s3/ debian/.debhelper/generated/mariadb-plugin-oqgraph/ debian/mariadb-plugin-oqgraph/ debian/.debhelper/generated/mariadb-plugin-spider/ debian/mariadb-plugin-spider/ debian/.debhelper/generated/mariadb-plugin-gssapi-server/ debian/mariadb-plugin-gssapi-server/ debian/.debhelper/generated/mariadb-plugin-gssapi-client/ debian/mariadb-plugin-gssapi-client/ debian/.debhelper/generated/mariadb-plugin-cracklib-password-check/ debian/mariadb-plugin-cracklib-password-check/ debian/.debhelper/generated/mariadb-test/ debian/mariadb-test/ debian/rules override_dh_auto_install make[1]: Entering directory '/<<PKGBUILDDIR>>' RULES.override_dh_auto_install dh_testdir dh_testroot ********************* The test suite is not starting at all! If there are any m68k experts in Debian who could look into this, and report their findings directly upstream at jira.mariadb.org so that an improved test (or underlying code fix) can be produced, it would be appreciated. If you have a patch: - Universal fixes are welcome directly upstream at https://github.com/mariadb/server - Debian-only fixes are welcome as Merge Requests at https://salsa.debian.org/mariadb-team/mariadb-10.5 I tagged this FTBFS so that the anomaly will be visible on the overview page at https://buildd.debian.org/status/package.php?p=mariadb-10.5 As the test suite does not run, we have not way of validating automatically that the binaries did build successfully. They might as well segfault immediately when started etc.