Related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972057

I noticed in the sh4 build log that the test suite does not start
after the build:

*********************
Full log: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=sh4&ver=1%3A10.5.9-1&stamp=1617143952&raw=0:
*********************
make[1]: Entering directory '/<<PKGBUILDDIR>>'
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.sh4 ] || cat debian/unstable-tests.sh4 >>
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/rules override_dh_auto_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
RULES.override_dh_auto_install
*********************

For some unknown reason mtr does not start at all. Thus we don't know
if the sh4 build actually succeeded or not.

In a normal build it should look like:

*********************
Full log at: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=x32&ver=1%3A10.5.9-1&stamp=1614082043&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.x32 ] || cat debian/unstable-tests.x32 >>
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 \
[...]
*********************


This is how the debian/rules looks like:

 override_dh_auto_test:
     @echo "RULES.$@"
     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.$(DEB_HOST_ARCH) ] || cat
debian/unstable-tests.$(DEB_HOST_ARCH) >> mysql-test/unstable-tests
     # Run testsuite
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
     # 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=$(NUMJOBS) --skip-rpl --suite=main \
           --skip-test-list=unstable-tests
 endif


It is if as the line ` ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))`
always evaluated false..?

Dear submitter,

as the package mariadb-10.5 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1004944

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

This bug still exists for MariaDB 10.6.

In https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=sh4&ver=1%3A10.6.7-1&stamp=1645397551&raw=0
the build passes despite skipping the test suite:

...
[100%] Built target wsrep_check_version
make[3]: Leaving directory '/<<PKGBUILDDIR>>/builddir'
/usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/builddir/CMakeFiles 0
make[2]: Leaving directory '/<<PKGBUILDDIR>>/builddir'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
RULES.override_dh_auto_test
dh_testdir
# Ensure at least an empty file exists
touch mysql-test/unstable-tests
# Skip unstable tests if such are defined for arch
[ ! -f debian/unstable-tests.sh4 ] || cat debian/unstable-tests.sh4 >>
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 ...
rm -fr -- debian/.debhelper/generated/libmariadb-dev/ ...
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
RULES.override_dh_auto_install
dh_testdir
dh_testroot
...

Arch sh4 is also affected by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006528 which is
potentially a sporadic build failure

Hello Otto!

The testsuites are intentionally disabled on m68k and sh4 since these targets
used QEMU-based buildds. This is not a bug, so I suggest closing both bugs.

Adrian

Thanks for the info. Do you what is the mechanism that controls makes the
test suite being skipped on m68k/sh?

The buildds set the environment variable DEB_BUILD_OPTIONS="nobench nocheck".

Adrian

Root cause:

Both sh4 and m68k runin qemu builders and have
DEB_BUILD_OPTIONS="nobench nocheck" defined, so tests are skipped
intentionally.