Re: Bug#970353: mksh: Ignores "nocheck" in DEB_BUILD_OPTIONS
On Tue, 15 Sep 2020, John Paul Adrian Glaubitz wrote:
> >
> >> On m68k and sh4, the buildds are currently configured to pass
> >> "nocheck"
> >
> > Precisely for this reason, some packages in the archive ignore that on
> > these architectures.
> >
> > Without the testsuite we cannot reliably build due to bugs in the
> > toolchain, and it doesn’t run for long anyway.
>
> I understand the reasoning but it's nevertheless incorrect.
>
> If you want to see a testsuite being run, you can ask the buildd
> maintainers or test the package yourself. But you shouldn't arbitrarily
> override policy-defined mechanisms so that a package behaves
> unexpectedly.
>
Arguably, downstream should try to avoid arbitrarily overriding upstream
policy. But instead of arbitrating the arbiters, perhaps we can discuss
the root cause.
> "nocheck" will remain activated as long as we're using qemu-user over
> qemu-system which will be the case until the kernel on the affected
> architectures can use more RAM on emulated systems.
>
I think it would be helpful to everyone if nocheck could be avoided where
possible. I wonder where is that possible.
Which architectures are using nocheck?
Why is it needed for qemu-user on m68k?
Would it help if test failures could be triaged, such that an "ENOMEM"
result could be treated as "undecided", since that is what it is?
Reply to: