[Debian-med-packaging] Please check maybe-failed of bali-phy
Cheng Li
shiptux at gmail.com
Tue Nov 3 14:03:16 GMT 2026
Hi Andreas,
> the bali-phy package is not migrating due to
>
> https://buildd.debian.org/status/logs.php?suite=sid&arch=riscv64&pkg=bali-phy&ver=4.3%2Bdfsg-2
>
> Can you help handling this?
I looked at the build log. This does not look like an architecture
problem: three tests simply do not finish within their timeout on the
riscv64 buildd and get killed.
>From the test summary in the log:
Ok: 785
Fail: 0
Timeout: 3
So 3 out of 788, and no failures. All three were killed by signal 15
(SIGTERM), and there are no architecture-specific errors and no wrong
results anywhere in the log.
The timeouts for these three tests are hardcoded in src/meson.build:
176-181 generated alignment program standalone timeout: 600 needs ~720s
184-185 bali-phy 5d test timeout: 300 needs ~370s
186-187 bali-phy 5d +A 50 timeout: 300 needs ~460s
The estimates come from comparing the 161 tests that pass on both
riscv64 and armhf and take more than 5s: riscv64 is roughly 11x (median)
slower than armhf. All three estimates are above the current limits, and
close enough to them that the tests were most likely still progressing
rather than stuck.
Note that bali-phy 48 +A 3 took 487.89s against a 600s limit, only 19%
headroom, so it is likely to be the next one to time out.
As for a fix, we could raise the timeouts via dh_auto_test:
dh_auto_test -- --timeout-multiplier 3
If that sounds reasonable, I am happy to report this as a bug and
provide a patch.
Kind regards,
Cheng Li
More information about the Debian-med-packaging
mailing list