Source: gnuradio
Version: 3.8.0.0-6
Severity: normal

>From the buildd log:

if case "amd64" in *"i386"*) false;; *) true;; esac; then
HOME=/<<PKGBUILDDIR>>/debian/test dh_auto_test -- ARGS+='--timeout 10 -E
systematic' ; fi
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test
"ARGS+=--timeout 10 -E systematic"
ninja: error: unknown target 'ARGS+=--timeout 10 -E systematic'
dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4
ninja test "ARGS+=--timeout 10 -E systematic" returned exit code 1
make[1]: [debian/rules:17: override_dh_auto_test] Error 255 (ignored)
rm -rf debian/test

The failure to actually run any test makes the build not actually run any
tests.

(And if I remove the ARGS+= part, I run into an endlessly running test case
115 qa_polar_decoder_sc_systematic - probably because it can't determine
the architecture properly on my build system and always returns the default
implementation, but I'm not sure.)

On a side note: If the system happens to still have python3.6 installed,
but python3 being python3.7 (and python3-dev using 3.7 as well), the build
fails because cmake seems to test for python3.6 first when determining the
python executable. Explicitly setting the python executable to python3
avoids that failure.

-- System Information:
Debian Release: bullseye/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US: (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Reply via email to