<div dir="ltr"><div>(First: An enormous thanks to inifinity0 and others who have been tracking down the build failures each release.)</div><div><br></div>I think somehow we need to "better align upstream+our incentives" - I assume all parties want to see Rust well supported on lots of architectures, we just have to remove whatever is preventing that.<div><br></div><div>I think to do that we have to somehow make the Debian buildd farm available for upstream, and encourage upstream to test/check releases against our architectures.</div><div><br></div><div>I suspect this means building some sort of pre-release (either beta or nightly) - presumably via experimental on all Debian archs. I suspect it will need to be nightly in order to be swift enough for upstream to get into a useful break-fix-check feedback loop. If we get this right, we should be able to step out of the critical path and just let upstream deal directly with our build reports.</div><div><br></div><div>Then we need to make build breakages prominent enough for upstream to notice. Automatically filing bugs (perhaps - only useful if we can keep the false positives very low), prominent build status reports, or something. Not sure what other options we have here...</div><div><br></div><div>Re testing migration: I think there's something to be said for just allowing the occasional version to be held back from testing migration. If we fall several versions behind in testing because it's broken on mips (eg), then I suspect this will fix itself one way or another once mozilla et al start shipping higher priority things that demand newer rustc's. Again, if we "hide" failures by whitelisting architectures, or skipping entire testsuites then we're also just hiding the failures from upstream. I'd like it if we could come up with some way that left build failures prominent but also removed the pressure infinity0 is feeling from having to chase every failure on every release.</div><div><br></div><div> - Gus</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, 29 Dec 2016 at 09:12 Sylvestre Ledru <<a href="mailto:Sylvestre@debian.org">Sylvestre@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_msg">From the issues I saw in the past, test failures seemed minimal to me, corner cases without impact on the overall quality of the compiler. <br class="gmail_msg">
In most of the rust releases, we are already ignoring some tests. <br class="gmail_msg">
<br class="gmail_msg">
If we are talking about a few tests failing, I would not set on the team unreasonable goals. <br class="gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"></div></div><div class="gmail_msg"><div class="gmail_quote gmail_msg">Le 28 décembre 2016 23:00:22 GMT+01:00, Josh Triplett <<a href="mailto:josh@joshtriplett.org" class="gmail_msg" target="_blank">josh@joshtriplett.org</a>> a écrit :</div></div><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><pre class="m_4487854582829076196k9mail gmail_msg">On Wed, Dec 28, 2016 at 03:40:00PM +0000, Ximin Luo wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #729fcf;padding-left:1ex"> Sylvestre Ledru:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #ad7fa8;padding-left:1ex"> Le 26/12/2016 à 15:43, Ximin Luo a écrit :<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #8ae234;padding-left:1ex"> Rust upstream does not regularly run tests for anything other than amd64 or i386:<br class="gmail_msg"><br class="gmail_msg"> <a href="https://forge.rust-lang.org/platform-support.html" class="gmail_msg" target="_blank">https://forge.rust-lang.org/platform-support.html</a><br class="gmail_msg"><br class="gmail_msg"> 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:<br class="gmail_msg"><br class="gmail_msg"> 1.10.0 <a href="https://github.com/rust-lang/rust/pull/34889" class="gmail_msg" target="_blank">https://github.com/rust-lang/rust/pull/34889</a><br class="gmail_msg"> 1.11.0 <a href="https://github.com/rust-lang/rust/issues/36348" class="gmail_msg" target="_blank">https://github.com/rust-lang/rust/issues/36348</a><br class="gmail_msg"> 1.12.0 there probably was one but I can't remember it<br class="gmail_msg"> 1.13.0 <a href="https://github.com/rust-lang/rust/issues/37225" class="gmail_msg" target="_blank">https://github.com/rust-lang/rust/issues/37225</a><br class="gmail_msg"> 1.14.0 <a href="https://github.com/rust-lang/rust/issues/38612" class="gmail_msg" target="_blank">https://github.com/rust-lang/rust/issues/38612</a><br class="gmail_msg"><br class="gmail_msg"> 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.<br class="gmail_msg"><br class="gmail_msg"> 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:<br class="gmail_msg"></blockquote> Or we could just fail at
build time on tier-1 and continue if the<br class="gmail_msg"> testsuite fails on the other archs.<br class="gmail_msg"> To be honest, this is what I am doing with LLVM & Clang...<br class="gmail_msg"> <br class="gmail_msg"></blockquote> <br class="gmail_msg"> 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.<br class="gmail_msg"></blockquote><br class="gmail_msg">I don't think we should ship builds in unstable/testing/stable that<br class="gmail_msg">don't pass Rust's extensive testsuite. Perhaps in experimental.<br class="gmail_msg"><br class="gmail_msg">- Josh Triplett<br class="gmail_msg"><br class="gmail_msg"><hr class="gmail_msg"><br class="gmail_msg"></pre></blockquote></div></div><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><pre class="m_4487854582829076196k9mail gmail_msg">Pkg-rust-maintainers mailing list<br class="gmail_msg"><a href="mailto:Pkg-rust-maintainers@lists.alioth.debian.org" class="gmail_msg" target="_blank">Pkg-rust-maintainers@lists.alioth.debian.org</a><br class="gmail_msg"><a href="https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers" class="gmail_msg" target="_blank">https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers</a><br class="gmail_msg"></pre></blockquote></div></div><div class="gmail_msg"><br class="gmail_msg">
-- <br class="gmail_msg">
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.</div>_______________________________________________<br class="gmail_msg">
Pkg-rust-maintainers mailing list<br class="gmail_msg">
<a href="mailto:Pkg-rust-maintainers@lists.alioth.debian.org" class="gmail_msg" target="_blank">Pkg-rust-maintainers@lists.alioth.debian.org</a><br class="gmail_msg">
<a href="https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers</a><br class="gmail_msg">
</blockquote></div>