[Debian-med-packaging] Please check maybe-failed of bali-phy
Cheng Li
shiptux at gmail.com
Fri Nov 6 12:40:58 GMT 2026
Hi Andreas,
> 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
It turned out that upstream already uses meson test suites elsewhere in
src/meson.build, so instead of a new build option the patch just tags the
long-running tests into a "heavy" suite. A slow machine can then skip them
with "meson test --no-suite heavy". No timeout is changed and no test is
removed, and I checked that a test carrying a suite keyword still runs when
meson test is invoked without a filter, so upstream's own test runs and CI
are unaffected.
If it gets merged, the Debian side would be a matter of passing
"--no-suite heavy" to dh_auto_test on the slow architectures, which I will
leave to you.
Kind regards,
Cheng Li
More information about the Debian-med-packaging
mailing list