[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1071085: chr: FTBFS on riscv64 due to test timeout



Source: chr
Version: 0.1.78-1
Severity: important
Tags: ftbfs
X-Debbugs-Cc: debian-riscv@lists.debian.org
User: debian-riscv@lists.debian.org
Usertags: riscv64

Dear maintainer,

chr fails to build from source on riscv64 (and a few other slow
architectures) with a timeout in a test:

| tests time out (After 30 seconds)
| ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
| 1/1 tests TIMEOUT        30.07s   killed by signal 15 SIGTERM
| 
| 
| Ok:                 0
| Expected Fail:      0
| Fail:               0
| Unexpected Pass:    0
| Skipped:            0
| Timeout:            1

The full build log is available there:
https://buildd.debian.org/status/fetch.php?pkg=chr&arch=riscv64&ver=0.1.78-1&stamp=1715582047&raw=0

After investigation, it appears the test actually passes, but needs 68
seconds instead of the default 30 seconds it got allocated. The
following patch uses the --timeout-multiplier feature of meson to
increase the timeout. I didn't try to use a different multiplier
depending on the architecture as it has no impact on working tests.


diff -Nru chr-0.1.78/debian/rules chr-0.1.78/debian/rules
--- chr-0.1.78/debian/rules
+++ chr-0.1.78/debian/rules
@@ -22,8 +22,8 @@
 	dh_auto_build --builddirectory=$(build_tiny)
 
 override_dh_auto_test:
-	dh_auto_test --builddirectory=$(build_edit)
-	dh_auto_test --builddirectory=$(build_tiny)
+	dh_auto_test --builddirectory=$(build_edit) -- --timeout-multiplier=4
+	dh_auto_test --builddirectory=$(build_tiny) -- --timeout-multiplier=4
 
 override_dh_auto_install:
 	dh_auto_install --builddirectory=$(build_edit) --destdir=debian/chr


Note that it might also fix the same issue on hppa and sparc64.

Regards
Aurelien

Reply to: