[Pkg-rust-maintainers] Efficiently supporting (or not) other arches in the long term

Josh Triplett josh at joshtriplett.org
Wed Dec 28 22:00:22 UTC 2016

On Wed, Dec 28, 2016 at 03:40:00PM +0000, Ximin Luo wrote:
> Sylvestre Ledru:
> > Le 26/12/2016 à 15:43, Ximin Luo a écrit :
> >> Rust upstream does not regularly run tests for anything other than amd64 or i386:
> >>
> >> https://forge.rust-lang.org/platform-support.html
> >>
> >> This has resulted in the past few releases of Debian's rustc being held back from testing migration, due to arm64 breakages that we had to file upstream:
> >>
> >> 1.10.0 https://github.com/rust-lang/rust/pull/34889
> >> 1.11.0 https://github.com/rust-lang/rust/issues/36348
> >> 1.12.0 there probably was one but I can't remember it
> >> 1.13.0 https://github.com/rust-lang/rust/issues/37225
> >> 1.14.0 https://github.com/rust-lang/rust/issues/38612
> >>
> >> We can't keep doing this long-term, I don't have time to chase these things every 6 weeks. And soon we might start supporting 7 new architectures, which will have their own test failures.
> >>
> >> What shall we do about this? I think it's nice to support as many architectures as possible, and that is strongly encouraged by Debian - but upstream don't provide the same level of support. I'll suggest two options:
> > Or we could just fail at build time on tier-1 and continue if the
> > testsuite fails on the other archs.
> > To be honest, this is what I am doing with LLVM & Clang...
> > 
> I'm reluctant to do this, because I don't know if these failures would cause buggy behaviour or security problems. If we do this, at least we should somehow make it very clear to users that the other platforms have these problems, and perhaps even include the test failure logs in the binary package.

I don't think we should ship builds in unstable/testing/stable that
don't pass Rust's extensive testsuite.  Perhaps in experimental.

- Josh Triplett

More information about the Pkg-rust-maintainers mailing list