On Sun, Jan 19, 2025 at 5:54 PM Aurelien Jarno <aure...@debian.org> wrote: > libsoup3 fails to build from source on riscv64. It seems to be a mix of > flaky tests like on other architectures and a riscv64 specific way of > failing: > > | Summary of Failures: > | > | 25/38 server-test ERROR 60.96s killed by signal > 11 SIGSEGV > | > | Ok: 37 > | Expected Fail: 0 > | Fail: 1 > | Unexpected Pass: 0 > | Skipped: 0 > | Timeout: 0 > | dh_auto_test: error: cd obj-riscv64-linux-gnu && > DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test > --verbose --timeout-multiplier 5 returned exit code 1 > | make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 25 > | make[1]: Leaving directory '/build/reproducible-path/libsoup3-3.6.4' > | make: *** [debian/rules:25: binary-arch] Error 2 > | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit > status 2 > | > -------------------------------------------------------------------------------- > | Build finished at 2025-01-19T19:51:21Z > > > The full build log is available there: > https://buildd.debian.org/status/fetch.php?pkg=libsoup3&arch=riscv64&ver=3.6.4-1&stamp=1737316290&raw=0 > > Although reported as a SIGSEGV, itIt appears that the test timeout is > too short for the riscv64 build daemons. Increasing the timeout > multiplier from 5 to 6, like in the patch below, allows the testsuite to > pass.
I applied your change and the riscv64 build completed on the second try. Notably, the success for 25/38 server-test only took 1.06s, so perhaps your change wasn't necessary. https://buildd.debian.org/status/logs.php?pkg=libsoup3&arch=riscv64 Thank you, Jeremy Bícha
