[Debian-med-packaging] Please check maybe-failed of bali-phy

Andreas Tille tille at debian.org
Sun Nov 8 06:06:50 GMT 2026


Hi Cheng Li,

thank you for working on this.

Am Sat, Nov 07, 2026 at 08:40:07PM +0900 schrieb Cheng Li:
> > I think the optimal solution would be some flag HEAVY_TESTS (or so) in
> > upstream test which we can switch off from debian/rules for selected
> > architectures.
> >
> > I'd welcome if you would create a MR upstream implementing this.
> 
> Done, as a pull request since that is what upstream's CONTRIBUTING.md asks
> for:
> 
>   https://github.com/bredelings/BAli-Phy/pull/33

Thank you for your work on this.
 
> But I think we should not use it, and I may close the PR. Upstream is already
> fixing the cause:
> ...
> riscv64 is about 11x slower than armhf on this package, taking the median over
> the 784 tests that pass on both, so a 10x on the tests themselves puts it at
> roughly armhf speed, where nothing is near its limit. A skip-list in
> debian/rules would then be dead weight that hides a real regression later. I
> would rather wait for his work than patch anything on our side.

OK, so it might be sensible to wait for the next upstream release.

> Two things for later. The slowest riscv64 tests are not the three that fail:
> prob_prog/infer_tree/yule/1 takes 195.98s against its 300s limit and 29 tests
> use more than a third of theirs, so that is where the next timeout will come
> from if the speedup does not reach them. And upstream offered to continue the
> discussion on a Debian list rather than in the PR -- would you rather have that
> on debian-med at lists.debian.org, or here?

As I said upstream is very cooperative.  Using debian-med at l.d.o makes perfectly
sense.

Thanks a lot for your work
    Andreas. 

-- 
https://fam-tille.de



More information about the Debian-med-packaging mailing list