Debian Bug report logs - #881845

rustc: FTBFS on mips*: test failures

Reported by: Emilio Pozuelo Monfort <pochu@debian.org> Date: Wed, 15 Nov 2017 17:33:02 UTC Severity: important Tags: confirmed, fixed-upstream, ftbfs, upstream Merged with 909482 Found in version rustc/1.21.0+dfsg1-3 Fixed in version rustc/1.30.0+dfsg1-1 Done: Ximin Luo <infinity0@debian.org> Bug is archived. No further changes may be made. Forwarded to https://bugs.llvm.org/show_bug.cgi?id=32020

Toggle useless messages

Report forwarded to debian-bugs-dist@lists.debian.org, pochu@debian.org, debian-mips@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Wed, 15 Nov 2017 17:33:04 GMT) (full text, mbox, link).

Acknowledgement sent to Emilio Pozuelo Monfort <pochu@debian.org> :

New Bug report received and forwarded. Copy sent to pochu@debian.org, debian-mips@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Wed, 15 Nov 2017 17:33:04 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: rustc: FTBFS on mips*: test failures Date: Wed, 15 Nov 2017 18:30:15 +0100

Source: rustc Version: 1.21.0+dfsg1-3 Severity: important Hi, Sometime ago I asked about rustc bootstrap status on mips*: 17:08 < infinity0> mips* fail many tests last time i tried, ~3 months ago, i didn't want to ship it, i haven't had time to check since From https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips&ver=1.14.0%2Bdfsg1-3&stamp=1484077706&raw=0 test net::tcp::tests::timeouts ... FAILED test net::udp::tests::timeouts ... FAILED test sys::imp::ext::net::test::timeouts ... FAILED Looks like timeouts are broken on rust/mips? mips64el has different errors: test f32::f32::tanh_0 ... FAILED test f64::f64::tanh_0 ... FAILED test io::error::Error::from_raw_os_error_0 ... FAILED Maybe the mips porters can take a look? (debian-mips@ on Cc). Note those errors are for 1.14.0, you'll want to try with a newer version first and see what's the current status. Emilio

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Fri, 17 Nov 2017 12:27:02 GMT) (full text, mbox, link).

Acknowledgement sent to James Cowgill <jcowgill@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Fri, 17 Nov 2017 12:27:02 GMT) (full text, mbox, link).

Message #10 received at 881845@bugs.debian.org (full text, mbox, reply):

From: James Cowgill <jcowgill@debian.org> To: Emilio Pozuelo Monfort <pochu@debian.org> Cc: 881845@bugs.debian.org, debian-mips@lists.debian.org Subject: Re: Bug#881845: rustc: FTBFS on mips*: test failures Date: Fri, 17 Nov 2017 12:25:35 +0000

Hi, On 15/11/17 17:30, Emilio Pozuelo Monfort wrote: > Source: rustc > Version: 1.21.0+dfsg1-3 > Severity: important > > Hi, > > Sometime ago I asked about rustc bootstrap status on mips*: > > 17:08 < infinity0> mips* fail many tests last time i tried, ~3 months ago, i didn't want to ship it, i haven't had time to check since > >>From https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips&ver=1.14.0%2Bdfsg1-3&stamp=1484077706&raw=0 > > test net::tcp::tests::timeouts ... FAILED > test net::udp::tests::timeouts ... FAILED > test sys::imp::ext::net::test::timeouts ... FAILED > > Looks like timeouts are broken on rust/mips? > > mips64el has different errors: > > test f32::f32::tanh_0 ... FAILED > test f64::f64::tanh_0 ... FAILED > test io::error::Error::from_raw_os_error_0 ... FAILED > > Maybe the mips porters can take a look? (debian-mips@ on Cc). Note those > errors are for 1.14.0, you'll want to try with a newer version first and > see what's the current status. I just tried building the latest rustc on mips64el. As I expected, I hit this LLVM bug again where any code using atomics will hang: https://bugs.llvm.org/show_bug.cgi?id=32020 I'll see if I can get Simon to have a look at it again. James

Set Bug forwarded-to-address to 'https://bugs.llvm.org/show_bug.cgi?id=32020'. Request was from Mathieu Malaterre <malat@debian.org> to control@bugs.debian.org . (Fri, 17 Nov 2017 13:00:03 GMT) (full text, mbox, link).

Added tag(s) confirmed and upstream. Request was from Mathieu Malaterre <malat@debian.org> to control@bugs.debian.org . (Fri, 17 Nov 2017 13:00:03 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Sat, 09 Dec 2017 11:27:05 GMT) (full text, mbox, link).

Acknowledgement sent to Emilio Pozuelo Monfort <pochu@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Sat, 09 Dec 2017 11:27:05 GMT) (full text, mbox, link).

Message #19 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org> To: 881845@bugs.debian.org, James Cowgill <jcowgill@debian.org>, "debian-mips@lists.debian.org" <debian-mips@lists.debian.org> Subject: Re: Bug#881845: rustc: FTBFS on mips*: test failures Date: Sat, 9 Dec 2017 12:23:36 +0100

On Fri, 17 Nov 2017 12:25:35 +0000 James Cowgill <jcowgill@debian.org> wrote: > Hi, > > On 15/11/17 17:30, Emilio Pozuelo Monfort wrote: > > Source: rustc > > Version: 1.21.0+dfsg1-3 > > Severity: important > > > > Hi, > > > > Sometime ago I asked about rustc bootstrap status on mips*: > > > > 17:08 < infinity0> mips* fail many tests last time i tried, ~3 months ago, i didn't want to ship it, i haven't had time to check since > > > >>From https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips&ver=1.14.0%2Bdfsg1-3&stamp=1484077706&raw=0 > > > > test net::tcp::tests::timeouts ... FAILED > > test net::udp::tests::timeouts ... FAILED > > test sys::imp::ext::net::test::timeouts ... FAILED > > > > Looks like timeouts are broken on rust/mips? > > > > mips64el has different errors: > > > > test f32::f32::tanh_0 ... FAILED > > test f64::f64::tanh_0 ... FAILED > > test io::error::Error::from_raw_os_error_0 ... FAILED > > > > Maybe the mips porters can take a look? (debian-mips@ on Cc). Note those > > errors are for 1.14.0, you'll want to try with a newer version first and > > see what's the current status. > > I just tried building the latest rustc on mips64el. As I expected, I hit > this LLVM bug again where any code using atomics will hang: > > https://bugs.llvm.org/show_bug.cgi?id=32020 > > I'll see if I can get Simon to have a look at it again. Any luck there? (I don't see a ping on the bug report). librsvg is now using rustc. We're stuck with an old version for now, but when we upgrade to the rust version, I wouldn't want to have to remove it, along with all the rdeps, from a bunch of architectures... Hence my insistence :) Cheers, Emilio

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Thu, 11 Jan 2018 20:21:06 GMT) (full text, mbox, link).

Acknowledgement sent to Emilio Pozuelo Monfort <pochu@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Thu, 11 Jan 2018 20:21:06 GMT) (full text, mbox, link).

Message #24 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org> To: James Cowgill <jcowgill@debian.org> Cc: 881845@bugs.debian.org, debian-mips@lists.debian.org Subject: Re: Bug#881845: rustc: FTBFS on mips*: test failures Date: Thu, 11 Jan 2018 21:16:27 +0100

On 17/11/17 13:25, James Cowgill wrote: > Hi, > > On 15/11/17 17:30, Emilio Pozuelo Monfort wrote: >> Source: rustc >> Version: 1.21.0+dfsg1-3 >> Severity: important >> >> Hi, >> >> Sometime ago I asked about rustc bootstrap status on mips*: >> >> 17:08 < infinity0> mips* fail many tests last time i tried, ~3 months ago, i didn't want to ship it, i haven't had time to check since >> >> >From https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips&ver=1.14.0%2Bdfsg1-3&stamp=1484077706&raw=0 >> >> test net::tcp::tests::timeouts ... FAILED >> test net::udp::tests::timeouts ... FAILED >> test sys::imp::ext::net::test::timeouts ... FAILED >> >> Looks like timeouts are broken on rust/mips? >> >> mips64el has different errors: >> >> test f32::f32::tanh_0 ... FAILED >> test f64::f64::tanh_0 ... FAILED >> test io::error::Error::from_raw_os_error_0 ... FAILED >> >> Maybe the mips porters can take a look? (debian-mips@ on Cc). Note those >> errors are for 1.14.0, you'll want to try with a newer version first and >> see what's the current status. > > I just tried building the latest rustc on mips64el. As I expected, I hit > this LLVM bug again where any code using atomics will hang: > > https://bugs.llvm.org/show_bug.cgi?id=32020 > > I'll see if I can get Simon to have a look at it again. FTR: According to our conversation over IRC, there's a patch for the above bug, but mips64el is now affected by https://github.com/rust-lang/rust/issues/47290 mips(el) may be fine now with that patch, or they may not :P Cheers, Emilio

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Fri, 02 Feb 2018 12:18:03 GMT) (full text, mbox, link).

Acknowledgement sent to James Cowgill <jcowgill@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Fri, 02 Feb 2018 12:18:03 GMT) (full text, mbox, link).

Message #29 received at 881845@bugs.debian.org (full text, mbox, reply):

From: James Cowgill <jcowgill@debian.org> To: Emilio Pozuelo Monfort <pochu@debian.org>, 881845@bugs.debian.org Cc: debian-mips@lists.debian.org Subject: Re: Bug#881845: rustc: FTBFS on mips*: test failures Date: Fri, 2 Feb 2018 12:14:03 +0000

Hi, On 11/01/18 20:16, Emilio Pozuelo Monfort wrote: > On 17/11/17 13:25, James Cowgill wrote: >> Hi, >> >> On 15/11/17 17:30, Emilio Pozuelo Monfort wrote: >>> Source: rustc >>> Version: 1.21.0+dfsg1-3 >>> Severity: important >>> >>> Hi, >>> >>> Sometime ago I asked about rustc bootstrap status on mips*: >>> >>> 17:08 < infinity0> mips* fail many tests last time i tried, ~3 months ago, i didn't want to ship it, i haven't had time to check since >>> >>> >From https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips&ver=1.14.0%2Bdfsg1-3&stamp=1484077706&raw=0 >>> >>> test net::tcp::tests::timeouts ... FAILED >>> test net::udp::tests::timeouts ... FAILED >>> test sys::imp::ext::net::test::timeouts ... FAILED >>> >>> Looks like timeouts are broken on rust/mips? >>> >>> mips64el has different errors: >>> >>> test f32::f32::tanh_0 ... FAILED >>> test f64::f64::tanh_0 ... FAILED >>> test io::error::Error::from_raw_os_error_0 ... FAILED >>> >>> Maybe the mips porters can take a look? (debian-mips@ on Cc). Note those >>> errors are for 1.14.0, you'll want to try with a newer version first and >>> see what's the current status. >> >> I just tried building the latest rustc on mips64el. As I expected, I hit >> this LLVM bug again where any code using atomics will hang: >> >> https://bugs.llvm.org/show_bug.cgi?id=32020 >> >> I'll see if I can get Simon to have a look at it again. > > FTR: > > According to our conversation over IRC, there's a patch for the above bug, but > mips64el is now affected by https://github.com/rust-lang/rust/issues/47290 > > mips(el) may be fine now with that patch, or they may not :P I have been looking at the state of rust support on mips over the last weeks or so. These are the major issues: Hanging atomics (mips, mipsel, mips64el) ==== This is an LLVM bug which happens on all mips. https://github.com/rust-lang/rust/issues/39013 https://bugs.llvm.org/show_bug.cgi?id=32020 I have attached the most recent iteration of Simon's LLVM fix for this along with some of my adjustments to it and a backport to LLVM 4.0 I used for testing with rust. LLVM 128-bit integer isues (mips, mipsel) ==== 128-bit integer arithmetic is broken in LLVM 4 on 32-bit MIPS. This has been fixed in LLVM 5. Unfortunately this bug has caused the upstream stage0 compiler to break badly so you may need to apply the fix and cross build your own stage0 until upstream binaries have moved to LLVM >= 5. https://github.com/rust-lang/rust/issues/41222 https://bugs.llvm.org/show_bug.cgi?id=32713 https://reviews.llvm.org/rL305389 llvm.powi.f64 broken (mips64el) ==== >>> test f32::f32::tanh_0 ... FAILED >>> test f64::f64::tanh_0 ... FAILED This is caused by the llvm.powi.f64 intrinsic being broken for negative powers. Thankfully this is not a very serious bug. Fixed here: https://bugs.llvm.org/show_bug.cgi?id=36061 https://reviews.llvm.org/D42537 No 64-bit Rust ABI support (mips64el) ==== The biggest issue with Rust itself is the lack of working FFI support for 64-bit mips. My attempt at implementing this: https://github.com/rust-lang/rust/issues/47290 https://github.com/rust-lang/rust/pull/47964 Other issues ==== >>> test net::tcp::tests::timeouts ... FAILED >>> test net::udp::tests::timeouts ... FAILED >>> test sys::imp::ext::net::test::timeouts ... FAILED As I wrote in https://github.com/rust-lang/rust/issues/39013, these are big endian specific. I haven't had the chance to test rust on big endian yet. >>> test io::error::Error::from_raw_os_error_0 ... FAILED Fixed in https://github.com/rust-lang/rust/pull/47874 Some FPU errors only happen on Loongson. In theory, enabling FPXX in LLVM should have fixed this, but I have not investigated it very far. There are a few other failing tests where the test itself is broken. I will try to submit fixes to ignore / adjust the tests soon. Thanks, James

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Mon, 28 May 2018 06:57:02 GMT) (full text, mbox, link).

Acknowledgement sent to Emilio Pozuelo Monfort <pochu@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Mon, 28 May 2018 06:57:02 GMT) (full text, mbox, link).

Message #34 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org> To: James Cowgill <jcowgill@debian.org>, 881845@bugs.debian.org Cc: debian-mips@lists.debian.org Subject: Re: Bug#881845: rustc: FTBFS on mips*: test failures Date: Mon, 28 May 2018 08:52:35 +0200

On 02/02/18 13:14, James Cowgill wrote: > Hi, > > On 11/01/18 20:16, Emilio Pozuelo Monfort wrote: >> On 17/11/17 13:25, James Cowgill wrote: >>> Hi, >>> >>> On 15/11/17 17:30, Emilio Pozuelo Monfort wrote: >>>> Source: rustc >>>> Version: 1.21.0+dfsg1-3 >>>> Severity: important >>>> >>>> Hi, >>>> >>>> Sometime ago I asked about rustc bootstrap status on mips*: >>>> >>>> 17:08 < infinity0> mips* fail many tests last time i tried, ~3 months ago, i didn't want to ship it, i haven't had time to check since >>>> >>>> >From https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips&ver=1.14.0%2Bdfsg1-3&stamp=1484077706&raw=0 >>>> >>>> test net::tcp::tests::timeouts ... FAILED >>>> test net::udp::tests::timeouts ... FAILED >>>> test sys::imp::ext::net::test::timeouts ... FAILED >>>> >>>> Looks like timeouts are broken on rust/mips? >>>> >>>> mips64el has different errors: >>>> >>>> test f32::f32::tanh_0 ... FAILED >>>> test f64::f64::tanh_0 ... FAILED >>>> test io::error::Error::from_raw_os_error_0 ... FAILED >>>> >>>> Maybe the mips porters can take a look? (debian-mips@ on Cc). Note those >>>> errors are for 1.14.0, you'll want to try with a newer version first and >>>> see what's the current status. >>> >>> I just tried building the latest rustc on mips64el. As I expected, I hit >>> this LLVM bug again where any code using atomics will hang: >>> >>> https://bugs.llvm.org/show_bug.cgi?id=32020 >>> >>> I'll see if I can get Simon to have a look at it again. >> >> FTR: >> >> According to our conversation over IRC, there's a patch for the above bug, but >> mips64el is now affected by https://github.com/rust-lang/rust/issues/47290 >> >> mips(el) may be fine now with that patch, or they may not :P > > I have been looking at the state of rust support on mips over the last > weeks or so. These are the major issues: > > Hanging atomics (mips, mipsel, mips64el) > ==== > This is an LLVM bug which happens on all mips. > > https://github.com/rust-lang/rust/issues/39013 > https://bugs.llvm.org/show_bug.cgi?id=32020 > > I have attached the most recent iteration of Simon's LLVM fix for this > along with some of my adjustments to it and a backport to LLVM 4.0 I > used for testing with rust. > > LLVM 128-bit integer isues (mips, mipsel) > ==== > 128-bit integer arithmetic is broken in LLVM 4 on 32-bit MIPS. This has > been fixed in LLVM 5. Unfortunately this bug has caused the upstream > stage0 compiler to break badly so you may need to apply the fix and > cross build your own stage0 until upstream binaries have moved to LLVM >= 5. > > https://github.com/rust-lang/rust/issues/41222 > https://bugs.llvm.org/show_bug.cgi?id=32713 > https://reviews.llvm.org/rL305389 > > llvm.powi.f64 broken (mips64el) > ==== >>>> test f32::f32::tanh_0 ... FAILED >>>> test f64::f64::tanh_0 ... FAILED > > This is caused by the llvm.powi.f64 intrinsic being broken for negative > powers. Thankfully this is not a very serious bug. > > Fixed here: > https://bugs.llvm.org/show_bug.cgi?id=36061 > https://reviews.llvm.org/D42537 > > No 64-bit Rust ABI support (mips64el) > ==== > The biggest issue with Rust itself is the lack of working FFI support > for 64-bit mips. > > My attempt at implementing this: > https://github.com/rust-lang/rust/issues/47290 > https://github.com/rust-lang/rust/pull/47964 > > Other issues > ==== >>>> test net::tcp::tests::timeouts ... FAILED >>>> test net::udp::tests::timeouts ... FAILED >>>> test sys::imp::ext::net::test::timeouts ... FAILED > > As I wrote in https://github.com/rust-lang/rust/issues/39013, these are > big endian specific. I haven't had the chance to test rust on big endian > yet. > >>>> test io::error::Error::from_raw_os_error_0 ... FAILED > > Fixed in https://github.com/rust-lang/rust/pull/47874 > > Some FPU errors only happen on Loongson. In theory, enabling FPXX in > LLVM should have fixed this, but I have not investigated it very far. > > There are a few other failing tests where the test itself is broken. I > will try to submit fixes to ignore / adjust the tests soon. Any progress on these issues? I see that rust built on mips64el but it now hangs. And mips/el are still uncompiled. Cheers, Emilio

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Mon, 28 May 2018 08:36:05 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Mon, 28 May 2018 08:36:05 GMT) (full text, mbox, link).

Message #39 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Emilio Pozuelo Monfort <pochu@debian.org>, 881845@bugs.debian.org, James Cowgill <jcowgill@debian.org> Cc: debian-mips@lists.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: rustc: FTBFS on mips*: test failures Date: Mon, 28 May 2018 10:33:22 +0200

On 05/28/2018 08:52 AM, Emilio Pozuelo Monfort wrote: > Any progress on these issues? I see that rust built on mips64el but it now > hangs. And mips/el are still uncompiled. I have not been able to build rustc natively on mips/mipsel because the process always runs out of memory when I try on minkus and eller. I tried the workaround from [1] to disable debuginfo for the standard library but that didn't help either. Adrian > [1] https://github.com/rust-lang/rust/issues/45854 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Sun, 15 Jul 2018 10:39:03 GMT) (full text, mbox, link).

Acknowledgement sent to Emilio Pozuelo Monfort <pochu@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Sun, 15 Jul 2018 10:39:03 GMT) (full text, mbox, link).

Message #44 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org> To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, 881845@bugs.debian.org, James Cowgill <jcowgill@debian.org> Cc: debian-mips@lists.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: rustc: FTBFS on mips*: test failures Date: Sun, 15 Jul 2018 12:33:55 +0200

Hi Adrian, On 28/05/18 10:33, John Paul Adrian Glaubitz wrote: > On 05/28/2018 08:52 AM, Emilio Pozuelo Monfort wrote: >> Any progress on these issues? I see that rust built on mips64el but it now >> hangs. And mips/el are still uncompiled. > > I have not been able to build rustc natively on mips/mipsel because the process > always runs out of memory when I try on minkus and eller. > > I tried the workaround from [1] to disable debuginfo for the standard library > but that didn't help either. Ok. I wonder if there are other options for us here. At what point does it run out of memory? Do you have a log? BTW mips64el is failing to build on the buildds. It only built there once, on eberlin. Is that the only mips64el buildd with an FPU? That could explain the timeouts. Cheers, Emilio

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Sun, 15 Jul 2018 10:48:02 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Sun, 15 Jul 2018 10:48:02 GMT) (full text, mbox, link).

Message #49 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Emilio Pozuelo Monfort <pochu@debian.org>, 881845@bugs.debian.org, James Cowgill <jcowgill@debian.org> Cc: debian-mips@lists.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: rustc: FTBFS on mips*: test failures Date: Sun, 15 Jul 2018 12:45:37 +0200

On 07/15/2018 12:33 PM, Emilio Pozuelo Monfort wrote: > Ok. I wonder if there are other options for us here. At what point does it run > out of memory? Do you have a log? I don't have a log, unfortunately, because I'm always building on eller or minkus where I cannot use sbuild but just run dpkg-buildpackage directly. I can, however, run the output through "tee" to get a logfile. The error looked very similar to the one we have seen on 32-Bit ARM targets, see [1]. The same workaround used for arm* in the debian/rules file didn't help on mips* though. > BTW mips64el is failing to build on the buildds. It only built there once, on > eberlin. Is that the only mips64el buildd with an FPU? That could explain the > timeouts. No idea. I just know there is apparently still a bug in the atomics code on mips* in LLVM, see [2]. Adrian > [1] https://github.com/rust-lang/rust/issues/45854 > [2] https://bugs.llvm.org/show_bug.cgi?id=32020 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Sun, 15 Jul 2018 14:57:07 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Sun, 15 Jul 2018 14:57:07 GMT) (full text, mbox, link).

Message #54 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: Emilio Pozuelo Monfort <pochu@debian.org>, 881845@bugs.debian.org, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, James Cowgill <jcowgill@debian.org> Cc: debian-mips@lists.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Sun, 15 Jul 2018 14:53:00 +0000

Emilio Pozuelo Monfort: > [..] > > Ok. I wonder if there are other options for us here. As the main rust maintainer IMO it's best to just RM the mips binaries so that testing migration works again. The LLVM bug on mips has been fixed recently with an insanely large patch, so it will eventually get in, but unless someone wants to spend their own time backporting it, mips is going to continue to fail and there's really no point keeping on trying to build it. Please RM it so other architectures get into Debian testing. We can try again later when the patch lands in LLVM. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Sun, 15 Jul 2018 15:03:02 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Sun, 15 Jul 2018 15:03:02 GMT) (full text, mbox, link).

Message #59 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Ximin Luo <infinity0@debian.org> Cc: Emilio Pozuelo Monfort <pochu@debian.org>, 881845@bugs.debian.org, James Cowgill <jcowgill@debian.org>, debian-mips@lists.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Sun, 15 Jul 2018 17:00:36 +0200

> On Jul 15, 2018, at 4:53 PM, Ximin Luo <infinity0@debian.org> wrote: > > Please RM it so other architectures get into Debian testing. We can try again later when the patch lands in LLVM. No need to reject, the packages already got rejected. Also, if there is a patch for LLVM to backport, I can do that, I have commit access. After that, I would start with mips64el first to avoid the memory issues. Adrian

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 12:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to Aron Xu <aron@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 12:33:03 GMT) (full text, mbox, link).

Message #64 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org> To: infinity0@debian.org Cc: Emilio Pozuelo Monfort <pochu@debian.org>, 881845@bugs.debian.org, Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, James Cowgill <jcowgill@debian.org>, debian-mips@lists.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 20:29:35 +0800

On Sun, Jul 15, 2018 at 11:18 PM Ximin Luo <infinity0@debian.org> wrote: > > Emilio Pozuelo Monfort: > > [..] > > > > Ok. I wonder if there are other options for us here. > > As the main rust maintainer IMO it's best to just RM the mips binaries so that testing migration works again. The LLVM bug on mips has been fixed recently with an insanely large patch, so it will eventually get in, but unless someone wants to spend their own time backporting it, mips is going to continue to fail and there's really no point keeping on trying to build it. > > Please RM it so other architectures get into Debian testing. We can try again later when the patch lands in LLVM. > As a temporary solution to unblock, I've built the package on a loongson-3a box and uploaded. It is the same hardware as eberlin.d.o, which in turn suggests this could be related to Cavium hardware. Cheers, Aron

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 14:39:03 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 14:39:03 GMT) (full text, mbox, link).

Message #69 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Aron Xu <aron@debian.org>, 881845@bugs.debian.org, infinity0@debian.org Cc: Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 16:36:19 +0200

On 07/17/2018 02:29 PM, Aron Xu wrote: > As a temporary solution to unblock, I've built the package on a > loongson-3a box and uploaded. It is the same hardware as eberlin.d.o, > which in turn suggests this could be related to Cavium hardware. Unless DSA is willing to blacklist the rustc package on the buildd hardware where it doesn't build (if that's actually the case), this won't work and will cause the package to FTBFS if it hits the wrong buildd. For Debian Ports, this would be acceptable. Don't know about release architectures though. The policy could be different there. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 14:45:03 GMT) (full text, mbox, link).

Acknowledgement sent to Aron Xu <aron@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 14:45:03 GMT) (full text, mbox, link).

Message #74 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org> To: Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: 881845@bugs.debian.org, infinity0@debian.org, Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 22:43:30 +0800

On Tue, Jul 17, 2018 at 10:36 PM John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote: > > On 07/17/2018 02:29 PM, Aron Xu wrote: > > As a temporary solution to unblock, I've built the package on a > > loongson-3a box and uploaded. It is the same hardware as eberlin.d.o, > > which in turn suggests this could be related to Cavium hardware. > > Unless DSA is willing to blacklist the rustc package on the buildd hardware > where it doesn't build (if that's actually the case), this won't work and > will cause the package to FTBFS if it hits the wrong buildd. > > For Debian Ports, this would be acceptable. Don't know about release architectures > though. The policy could be different there. > Binary only upload from porter is allowed but not encouraged, it works similar to an initial upload with source+binary. As said this is temporary, blacklisting is needed and we are just relaxing Rust maintainers from being worried too much about migration. Cheers, Aron

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 14:48:03 GMT) (full text, mbox, link).

Acknowledgement sent to Aron Xu <aron@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 14:48:03 GMT) (full text, mbox, link).

Message #79 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org> To: Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: 881845@bugs.debian.org, infinity0@debian.org, Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 22:45:50 +0800

On Tue, Jul 17, 2018 at 10:36 PM John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote: > > On 07/17/2018 02:29 PM, Aron Xu wrote: > > As a temporary solution to unblock, I've built the package on a > > loongson-3a box and uploaded. It is the same hardware as eberlin.d.o, > > which in turn suggests this could be related to Cavium hardware. > > Unless DSA is willing to blacklist the rustc package on the buildd hardware > where it doesn't build (if that's actually the case), this won't work and > will cause the package to FTBFS if it hits the wrong buildd. > > For Debian Ports, this would be acceptable. Don't know about release architectures > though. The policy could be different there. > Want to add that, on Debian Ports porters are allowed to include some trivial patches to make the package build/useful, while what I have done is a binary-only build without any source package change. Regards, Aron

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 14:51:03 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 14:51:03 GMT) (full text, mbox, link).

Message #84 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Aron Xu <aron@debian.org> Cc: 881845@bugs.debian.org, infinity0@debian.org, Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 16:47:32 +0200

On 07/17/2018 04:43 PM, Aron Xu wrote: > Binary only upload from porter is allowed but not encouraged, it works > similar to an initial upload with source+binary. Yes, I am fully aware how that works. I am a very active porter :). > As said this is temporary, blacklisting is needed and we are > just relaxing Rust maintainers from being worried too much > about migration. And you are missing an important part. The next time a new version of rustc gets upload, the package can end up on the wrong buildd and fail to build from source meaning that testing migration will be stuck. This is what my original mail was about. Unless you actively blacklist rustc from being built on the affected buildds through the buildds local configuration file, your workaround will not work. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 14:51:04 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 14:51:04 GMT) (full text, mbox, link).

Message #89 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Aron Xu <aron@debian.org> Cc: 881845@bugs.debian.org, infinity0@debian.org, Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 16:48:40 +0200

On 07/17/2018 04:45 PM, Aron Xu wrote: > Want to add that, on Debian Ports porters are allowed to include some > trivial patches to make the package build/useful, while what I have > done is a binary-only build without any source package change. Aron, with all due respect: 1) You assume I don't know how any of this works even though I have probably done much more in this field in Debian than you. 2) I don't think you understand what the actual problem is here. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 14:54:06 GMT) (full text, mbox, link).

Acknowledgement sent to Aron Xu <aron@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 14:54:06 GMT) (full text, mbox, link).

Message #94 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org> To: Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: 881845@bugs.debian.org, infinity0@debian.org, Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 22:51:49 +0800

On Tue, Jul 17, 2018 at 10:48 PM John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote: > > On 07/17/2018 04:45 PM, Aron Xu wrote: > > Want to add that, on Debian Ports porters are allowed to include some > > trivial patches to make the package build/useful, while what I have > > done is a binary-only build without any source package change. > > Aron, with all due respect: > > 1) You assume I don't know how any of this works even though I have > probably done much more in this field in Debian than you. > > 2) I don't think you understand what the actual problem is here. > I think you are too much defensive, while I don't mean offensive any how. The thing to fix this forever is either of: 1) Fix the software to make it build on all hardware; 2) Blacklist the package on hardware that fails to build it. You are just blaming blindly here, and this will be my last response to you on this very specific argument. Have a nice day, Aron

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 15:21:03 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 15:21:03 GMT) (full text, mbox, link).

Message #99 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Aron Xu <aron@debian.org>, 881845@bugs.debian.org Cc: Emilio Pozuelo Monfort <pochu@debian.org>, infinity0@debian.org, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 17:16:44 +0200

On 07/17/2018 04:51 PM, Aron Xu wrote: > I think you are too much defensive, while I don't mean offensive any how. Maybe you shouldn't automatically assume then that the other person doesn't know what they are talking about? > The thing to fix this forever is either of: > 1) Fix the software to make it build on all hardware; > 2) Blacklist the package on hardware that fails to build it. > > You are just blaming blindly here, and this will be my last response > to you on this very specific argument. Neither 1) nor 2) have happened, yet you decided to upload the package to unstable. Did you check back with the rust maintainers? rustc and cargo were already uploaded for mips64el and later removed because of the LLVM bug which made the package FTBFS on the buildds. I don't understand why you just went ahead and uploaded the package without seemingly checking back with the Rust maintainers. (Cross-)building and uploading rustc for a new architecture is not hard. Making the native compuiler actually work properly, on the other hand, is. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 16:09:03 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 16:09:03 GMT) (full text, mbox, link).

Message #104 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, 881845@bugs.debian.org, Aron Xu <aron@debian.org> Cc: Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 16:03:00 +0000

John Paul Adrian Glaubitz: > On 07/17/2018 04:51 PM, Aron Xu wrote: >> I think you are too much defensive, while I don't mean offensive any how. > > Maybe you shouldn't automatically assume then that the other person > doesn't know what they are talking about? > >> The thing to fix this forever is either of: >> 1) Fix the software to make it build on all hardware; >> 2) Blacklist the package on hardware that fails to build it. >> >> You are just blaming blindly here, and this will be my last response >> to you on this very specific argument. > Neither 1) nor 2) have happened, yet you decided to upload the > package to unstable. Did you check back with the rust maintainers? > > rustc and cargo were already uploaded for mips64el and later removed > because of the LLVM bug which made the package FTBFS on the buildds. > I don't understand why you just went ahead and uploaded the package > without seemingly checking back with the Rust maintainers. > > (Cross-)building and uploading rustc for a new architecture is not > hard. Making the native compuiler actually work properly, on the > other hand, is. > Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 16:12:03 GMT) (full text, mbox, link).

Acknowledgement sent to Aron Xu <aron@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 16:12:03 GMT) (full text, mbox, link).

Message #109 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Aron Xu <aron@debian.org> To: infinity0@debian.org Cc: Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, 881845@bugs.debian.org, Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Wed, 18 Jul 2018 00:09:36 +0800

On Wed, Jul 18, 2018 at 12:04 AM Ximin Luo <infinity0@debian.org> wrote: > > John Paul Adrian Glaubitz: > > On 07/17/2018 04:51 PM, Aron Xu wrote: > >> I think you are too much defensive, while I don't mean offensive any how. > > > > Maybe you shouldn't automatically assume then that the other person > > doesn't know what they are talking about? > > > >> The thing to fix this forever is either of: > >> 1) Fix the software to make it build on all hardware; > >> 2) Blacklist the package on hardware that fails to build it. > >> > >> You are just blaming blindly here, and this will be my last response > >> to you on this very specific argument. > > Neither 1) nor 2) have happened, yet you decided to upload the > > package to unstable. Did you check back with the rust maintainers? > > > > rustc and cargo were already uploaded for mips64el and later removed > > because of the LLVM bug which made the package FTBFS on the buildds. > > I don't understand why you just went ahead and uploaded the package > > without seemingly checking back with the Rust maintainers. > > > > (Cross-)building and uploading rustc for a new architecture is not > > hard. Making the native compuiler actually work properly, on the > > other hand, is. > > > > Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > > Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > Will do that and see if we can get the issue either fixed or have a blacklist placed at the same time. Cheers, Aron

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 17 Jul 2018 16:12:04 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 17 Jul 2018 16:12:04 GMT) (full text, mbox, link).

Message #114 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Ximin Luo <infinity0@debian.org>, 881845@bugs.debian.org, Aron Xu <aron@debian.org> Cc: Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 17 Jul 2018 18:10:14 +0200

On 07/17/2018 06:03 PM, Ximin Luo wrote: > Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. Well, I have to partially take my criticism back. Aron has pointed out on IRC that rustc was not yet removed for mips64el, I thought that had happened but indeed that wasn't the case, just cargo was removed. So, his upload didn't really change anything in this regard. > Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. DSA could blacklist rustc from being built on buildds other than eberlin but I assume they won't agree to applying such a hack. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Fri, 20 Jul 2018 15:18:02 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Fri, 20 Jul 2018 15:18:02 GMT) (full text, mbox, link).

Message #119 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: 881845@bugs.debian.org, Aurelien Jarno <aurel32@debian.org> Subject: Re: Bug#881845: rustc: FTBFS on mips*: test failures Date: Fri, 20 Jul 2018 23:15:58 +0800

On Tue, 17 Jul 2018 18:10:14 +0200 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote: > On 07/17/2018 06:03 PM, Ximin Luo wrote: > > Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > > Well, I have to partially take my criticism back. Aron has pointed out on IRC > that rustc was not yet removed for mips64el, I thought that had happened but > indeed that wasn't the case, just cargo was removed. > > So, his upload didn't really change anything in this regard. > > > Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > > DSA could blacklist rustc from being built on buildds other than eberlin > but I assume they won't agree to applying such a hack. I have asked Aurelien to blacklist rustc. @Aurelien, oh the rustc problem is not about `make', it is about llvm. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaubitz@debian.org > `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Fri, 20 Jul 2018 15:33:05 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Fri, 20 Jul 2018 15:33:05 GMT) (full text, mbox, link).

Message #124 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: YunQiang Su <wzssyqa@gmail.com>, 881845@bugs.debian.org Cc: Aurelien Jarno <aurel32@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: rustc: FTBFS on mips*: test failures Date: Fri, 20 Jul 2018 17:30:06 +0200

Blacklisting doesn’t fix the transition block. Once the package is outdated on any of the release architectures, transition is blocked. > On Jul 20, 2018, at 5:15 PM, YunQiang Su <wzssyqa@gmail.com> wrote: > > On Tue, 17 Jul 2018 18:10:14 +0200 John Paul Adrian Glaubitz > <glaubitz@physik.fu-berlin.de> wrote: >> On 07/17/2018 06:03 PM, Ximin Luo wrote: >>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. >> >> Well, I have to partially take my criticism back. Aron has pointed out on IRC >> that rustc was not yet removed for mips64el, I thought that had happened but >> indeed that wasn't the case, just cargo was removed. >> >> So, his upload didn't really change anything in this regard. >> >>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. >> >> DSA could blacklist rustc from being built on buildds other than eberlin >> but I assume they won't agree to applying such a hack. > > I have asked Aurelien to blacklist rustc. > @Aurelien, oh the rustc problem is not about `make', it is about llvm. > >> >> Adrian >> >> -- >> .''`. John Paul Adrian Glaubitz >> : :' : Debian Developer - glaubitz@debian.org >> `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de >> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >> >> > > _______________________________________________ > Pkg-rust-maintainers mailing list > Pkg-rust-maintainers@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 24 Jul 2018 01:09:03 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 24 Jul 2018 01:09:03 GMT) (full text, mbox, link).

Message #129 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: 881845@bugs.debian.org, Aurelien Jarno <aurel32@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 24 Jul 2018 09:04:47 +0800

1.27.1+dfsg1-1~exp4 still FTBFS. As rustc seems need big got. --- a/src/bootstrap/bootstrap.py +++ b/src/bootstrap/bootstrap.py @@ -590,7 +590,7 @@ env["LIBRARY_PATH"] = os.path.join(self.bin_root(), "lib") + \ (os.pathsep + env["LIBRARY_PATH"]) \ if "LIBRARY_PATH" in env else "" - env["RUSTFLAGS"] = "-Cdebuginfo=2" + env["RUSTFLAGS"] = "-Cdebuginfo=2 -Cllvm-args=-mxgot" env["PATH"] = os.path.join(self.bin_root(), "bin") + \ os.pathsep + env["PATH"] if not os.path.isfile(self.cargo()): --- a/src/vendor/cc/src/lib.rs +++ b/src/vendor/cc/src/lib.rs @@ -1106,6 +1106,8 @@ cmd.args.push("-mx32".into()); } else if target.contains("x86_64") || target.contains("powerpc64") { cmd.args.push("-m64".into()); + } else if target.contains("mips") { + cmd.args.push("-mxgot".into()); } if self.static_flag.is_none() { John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> 于2018年7月20日周五 下午11:30写道： > > Blacklisting doesn’t fix the transition block. > > Once the package is outdated on any of the release architectures, transition is blocked. > > > On Jul 20, 2018, at 5:15 PM, YunQiang Su <wzssyqa@gmail.com> wrote: > > > > On Tue, 17 Jul 2018 18:10:14 +0200 John Paul Adrian Glaubitz > > <glaubitz@physik.fu-berlin.de> wrote: > >> On 07/17/2018 06:03 PM, Ximin Luo wrote: > >>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > >> > >> Well, I have to partially take my criticism back. Aron has pointed out on IRC > >> that rustc was not yet removed for mips64el, I thought that had happened but > >> indeed that wasn't the case, just cargo was removed. > >> > >> So, his upload didn't really change anything in this regard. > >> > >>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > >> > >> DSA could blacklist rustc from being built on buildds other than eberlin > >> but I assume they won't agree to applying such a hack. > > > > I have asked Aurelien to blacklist rustc. > > @Aurelien, oh the rustc problem is not about `make', it is about llvm. > > > >> > >> Adrian > >> > >> -- > >> .''`. John Paul Adrian Glaubitz > >> : :' : Debian Developer - glaubitz@debian.org > >> `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de > >> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >> > >> > > > > _______________________________________________ > > Pkg-rust-maintainers mailing list > > Pkg-rust-maintainers@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 24 Jul 2018 23:18:02 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 24 Jul 2018 23:18:02 GMT) (full text, mbox, link).

Message #134 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: YunQiang Su <wzssyqa@gmail.com>, 881845@bugs.debian.org, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: Aurelien Jarno <aurel32@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 24 Jul 2018 23:14:00 +0000

Can you explain what this patch does and file it to Rust upstream first so I can see that they think it's OK? The first hunk seems like it should be conditioned on the target-architecture being mips64, rather than blanket applied to all architetcures. I'm also unsure if it's better being applied to ./src/librustc_target/spec/mips64{,el}_unknown_linux_gnuabi64.rs rather than these files. X YunQiang Su: > 1.27.1+dfsg1-1~exp4 still FTBFS. > As rustc seems need big got. > > --- a/src/bootstrap/bootstrap.py > +++ b/src/bootstrap/bootstrap.py > @@ -590,7 +590,7 @@ > env["LIBRARY_PATH"] = os.path.join(self.bin_root(), "lib") + \ > (os.pathsep + env["LIBRARY_PATH"]) \ > if "LIBRARY_PATH" in env else "" > - env["RUSTFLAGS"] = "-Cdebuginfo=2" > + env["RUSTFLAGS"] = "-Cdebuginfo=2 -Cllvm-args=-mxgot" > env["PATH"] = os.path.join(self.bin_root(), "bin") + \ > os.pathsep + env["PATH"] > if not os.path.isfile(self.cargo()): > --- a/src/vendor/cc/src/lib.rs > +++ b/src/vendor/cc/src/lib.rs > @@ -1106,6 +1106,8 @@ > cmd.args.push("-mx32".into()); > } else if target.contains("x86_64") || > target.contains("powerpc64") { > cmd.args.push("-m64".into()); > + } else if target.contains("mips") { > + cmd.args.push("-mxgot".into()); > } > > if self.static_flag.is_none() { -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Wed, 25 Jul 2018 01:15:03 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Wed, 25 Jul 2018 01:15:03 GMT) (full text, mbox, link).

Message #139 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: infinity0@debian.org Cc: 881845@bugs.debian.org, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, Aurelien Jarno <aurel32@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Wed, 25 Jul 2018 09:13:37 +0800

Ximin Luo <infinity0@debian.org> 于2018年7月25日周三 上午7:15写道： > > Can you explain what this patch does and file it to Rust upstream first so I can see that they think it's OK? MIPS's default GOT size is small for performance, while for some big app, they may complain GOT is too small. So there is an complier time option `-mxgot' to force big GOT. That is what we meet here. > > The first hunk seems like it should be conditioned on the target-architecture being mips64, rather than blanket applied to all architetcures. > Yes, you are right. Can you fix it when apply? > I'm also unsure if it's better being applied to ./src/librustc_target/spec/mips64{,el}_unknown_linux_gnuabi64.rs rather than these files. > > X > > YunQiang Su: > > 1.27.1+dfsg1-1~exp4 still FTBFS. > > As rustc seems need big got. > > > > --- a/src/bootstrap/bootstrap.py > > +++ b/src/bootstrap/bootstrap.py > > @@ -590,7 +590,7 @@ > > env["LIBRARY_PATH"] = os.path.join(self.bin_root(), "lib") + \ > > (os.pathsep + env["LIBRARY_PATH"]) \ > > if "LIBRARY_PATH" in env else "" > > - env["RUSTFLAGS"] = "-Cdebuginfo=2" > > + env["RUSTFLAGS"] = "-Cdebuginfo=2 -Cllvm-args=-mxgot" > > env["PATH"] = os.path.join(self.bin_root(), "bin") + \ > > os.pathsep + env["PATH"] > > if not os.path.isfile(self.cargo()): > > --- a/src/vendor/cc/src/lib.rs > > +++ b/src/vendor/cc/src/lib.rs > > @@ -1106,6 +1106,8 @@ > > cmd.args.push("-mx32".into()); > > } else if target.contains("x86_64") || > > target.contains("powerpc64") { > > cmd.args.push("-m64".into()); > > + } else if target.contains("mips") { > > + cmd.args.push("-mxgot".into()); > > } > > > > if self.static_flag.is_none() { > > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > https://github.com/infinity0/pubkeys.git -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Wed, 25 Jul 2018 03:03:03 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Wed, 25 Jul 2018 03:03:03 GMT) (full text, mbox, link).

Message #144 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: YunQiang Su <wzssyqa@gmail.com>, 881845@bugs.debian.org Cc: Aurelien Jarno <aurel32@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Wed, 25 Jul 2018 03:01:00 +0000

YunQiang Su: > Ximin Luo <infinity0@debian.org> 于2018年7月25日周三 上午7:15写道： >> >> Can you explain what this patch does and file it to Rust upstream first so I can see that they think it's OK? > > MIPS's default GOT size is small for performance, while for some big > app, they may complain GOT is too small. > So there is an complier time option `-mxgot' to force big GOT. > That is what we meet here. > >> >> The first hunk seems like it should be conditioned on the target-architecture being mips64, rather than blanket applied to all architetcures. >> > > Yes, you are right. Can you fix it when apply? > >> I'm also unsure if it's better being applied to ./src/librustc_target/spec/mips64{,el}_unknown_linux_gnuabi64.rs rather than these files. >> If -mxgot is required for all rust programs then the rustc upstream compiler should be patched to add this flag unconditionally, we shouldn't carry this patch in Debian. I'd also like to get some comments from the Rust Project upstream that this is in fact the right way to solve the issue. So from my position of ignorance I'm not yet confident enough to apply the patch like this, sorry. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Wed, 25 Jul 2018 04:12:09 GMT) (full text, mbox, link).

Acknowledgement sent to Seo Sanghyeon <sanxiyn@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Wed, 25 Jul 2018 04:12:09 GMT) (full text, mbox, link).

Message #149 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Seo Sanghyeon <sanxiyn@gmail.com> To: 881845@bugs.debian.org Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Wed, 25 Jul 2018 13:08:03 +0900

2018-07-25 12:01 GMT+09:00 Ximin Luo <infinity0@debian.org>: > If -mxgot is required for all rust programs then the rustc upstream compiler should be patched to add this flag unconditionally, we shouldn't carry this patch in Debian. The issue has been reported upstream as https://github.com/rust-lang/rust/issues/52108 and Dragan Mladjenovic promised PR. -- Seo Sanghyeon

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Wed, 01 Aug 2018 10:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Wed, 01 Aug 2018 10:33:03 GMT) (full text, mbox, link).

Message #154 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Cc: 881845@bugs.debian.org, Aurelien Jarno <aurel32@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: rustc: FTBFS on mips*: test failures Date: Wed, 1 Aug 2018 18:30:38 +0800

Index: rustc-1.27.1+dfsg1/src/bootstrap/bootstrap.py =================================================================== --- rustc-1.27.1+dfsg1.orig/src/bootstrap/bootstrap.py +++ rustc-1.27.1+dfsg1/src/bootstrap/bootstrap.py @@ -591,6 +591,8 @@ class RustBuild(object): (os.pathsep + env["LIBRARY_PATH"]) \ if "LIBRARY_PATH" in env else "" env["RUSTFLAGS"] = "-Cdebuginfo=2" + if self.build_triple().startswith('mips'): + env["RUSTFLAGS"] += " -Cllvm-args=-mxgot" env["PATH"] = os.path.join(self.bin_root(), "bin") + \ os.pathsep + env["PATH"] if not os.path.isfile(self.cargo()): This patch should work. And I pasted it on the upstream github. YunQiang Su <wzssyqa@gmail.com> 于2018年7月24日周二 上午9:04写道： > > 1.27.1+dfsg1-1~exp4 still FTBFS. > As rustc seems need big got. > > --- a/src/bootstrap/bootstrap.py > +++ b/src/bootstrap/bootstrap.py > @@ -590,7 +590,7 @@ > env["LIBRARY_PATH"] = os.path.join(self.bin_root(), "lib") + \ > (os.pathsep + env["LIBRARY_PATH"]) \ > if "LIBRARY_PATH" in env else "" > - env["RUSTFLAGS"] = "-Cdebuginfo=2" > + env["RUSTFLAGS"] = "-Cdebuginfo=2 -Cllvm-args=-mxgot" > env["PATH"] = os.path.join(self.bin_root(), "bin") + \ > os.pathsep + env["PATH"] > if not os.path.isfile(self.cargo()): > --- a/src/vendor/cc/src/lib.rs > +++ b/src/vendor/cc/src/lib.rs > @@ -1106,6 +1106,8 @@ > cmd.args.push("-mx32".into()); > } else if target.contains("x86_64") || > target.contains("powerpc64") { > cmd.args.push("-m64".into()); > + } else if target.contains("mips") { > + cmd.args.push("-mxgot".into()); > } > > if self.static_flag.is_none() { > John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> 于2018年7月20日周五 > 下午11:30写道： > > > > Blacklisting doesn’t fix the transition block. > > > > Once the package is outdated on any of the release architectures, transition is blocked. > > > > > On Jul 20, 2018, at 5:15 PM, YunQiang Su <wzssyqa@gmail.com> wrote: > > > > > > On Tue, 17 Jul 2018 18:10:14 +0200 John Paul Adrian Glaubitz > > > <glaubitz@physik.fu-berlin.de> wrote: > > >> On 07/17/2018 06:03 PM, Ximin Luo wrote: > > >>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > > >> > > >> Well, I have to partially take my criticism back. Aron has pointed out on IRC > > >> that rustc was not yet removed for mips64el, I thought that had happened but > > >> indeed that wasn't the case, just cargo was removed. > > >> > > >> So, his upload didn't really change anything in this regard. > > >> > > >>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > > >> > > >> DSA could blacklist rustc from being built on buildds other than eberlin > > >> but I assume they won't agree to applying such a hack. > > > > > > I have asked Aurelien to blacklist rustc. > > > @Aurelien, oh the rustc problem is not about `make', it is about llvm. > > > > > >> > > >> Adrian > > >> > > >> -- > > >> .''`. John Paul Adrian Glaubitz > > >> : :' : Debian Developer - glaubitz@debian.org > > >> `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de > > >> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > > >> > > >> > > > > > > _______________________________________________ > > > Pkg-rust-maintainers mailing list > > > Pkg-rust-maintainers@alioth-lists.debian.net > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > > > > > -- > YunQiang Su -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Sun, 23 Sep 2018 18:00:06 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Sun, 23 Sep 2018 18:00:06 GMT) (full text, mbox, link).

Message #159 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: Aron Xu <aron@debian.org>, 881845@bugs.debian.org Cc: Emilio Pozuelo Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org>, Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Sun, 23 Sep 2018 17:57:00 +0000

Aron Xu: > [..] >> >> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. >> >> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. >> > > Will do that and see if we can get the issue either fixed or have a > blacklist placed at the same time. > I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds E: Build killed with signal TERM after 150 minutes of inactivity I still think we should just RM rustc on mips64el. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Added tag(s) ftbfs. Request was from Ximin Luo <infinity0@debian.org> to 909482-submit@bugs.debian.org . (Tue, 25 Sep 2018 02:30:07 GMT) (full text, mbox, link).

Merged 881845 909482 Request was from Ximin Luo <infinity0@debian.org> to 909482-submit@bugs.debian.org . (Tue, 25 Sep 2018 02:30:08 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Thu, 27 Sep 2018 01:36:02 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Thu, 27 Sep 2018 01:36:02 GMT) (full text, mbox, link).

Message #168 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: infinity0@debian.org Cc: Aron Xu <aron@debian.org>, 881845@bugs.debian.org, PozueloEmilio Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Thu, 27 Sep 2018 09:33:36 +0800

It is still about llvm+octeon problem. Maybe we can ask pin rustc on Loongson machines. Ximin Luo <infinity0@debian.org> 于2018年9月24日周一 上午2:21写道： > > Aron Xu: > > [..] > >> > >> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > >> > >> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > >> > > > > Will do that and see if we can get the issue either fixed or have a > > blacklist placed at the same time. > > > > I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: > > https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 > > test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds > test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds > test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds > test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds > E: Build killed with signal TERM after 150 minutes of inactivity > > I still think we should just RM rustc on mips64el. > > X > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > https://github.com/infinity0/pubkeys.git > -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Thu, 27 Sep 2018 04:06:04 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Thu, 27 Sep 2018 04:06:04 GMT) (full text, mbox, link).

Message #173 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: YunQiang Su <wzssyqa@gmail.com>, 881845@bugs.debian.org Cc: debian-mips@lists.debian.org, Aron Xu <aron@debian.org>, PozueloEmilio Monfort <pochu@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, James Cowgill <jcowgill@debian.org>, Ivo De Decker <ivodd@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Thu, 27 Sep 2018 04:02:00 +0000

Do you have a link to a more detailed description of the problem, so that the rest of us can understand it? For example James in message 29 gave a very detailed summary of other previous problems: [29] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881845#29 Nobody in this thread has stated what the supposed problem actually is with these Cavium/Octeon machines. FYI the builds failed recently on eberlin and manda-03, and has failed in the past on aql-01. These are all octeon, and the other mips64el buildd sil-01 is also octeon. So it seems all our buildds are affected by the bug. So the blacklist approach won't even work. Also unless I can understand the problem, I don't feel happy using the blacklist as a temporary solution, even if it was going to work. X YunQiang Su: > It is still about llvm+octeon problem. > > Maybe we can ask pin rustc on Loongson machines. > Ximin Luo <infinity0@debian.org> 于2018年9月24日周一 上午2:21写道： >> >> Aron Xu: >>> [..] >>>> >>>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. >>>> >>>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. >>>> >>> >>> Will do that and see if we can get the issue either fixed or have a >>> blacklist placed at the same time. >>> >> >> I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: >> >> https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 >> >> test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds >> test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds >> test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds >> test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds >> E: Build killed with signal TERM after 150 minutes of inactivity >> >> I still think we should just RM rustc on mips64el. >> >> X >> >> -- >> GPG: ed25519/56034877E1F87C35 >> GPG: rsa4096/1318EFAC5FBBDBCE >> https://github.com/infinity0/pubkeys.git >> > > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Thu, 27 Sep 2018 04:09:02 GMT) (full text, mbox, link).

Acknowledgement sent to Ximin Luo <infinity0@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Thu, 27 Sep 2018 04:09:02 GMT) (full text, mbox, link).

Message #178 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Ximin Luo <infinity0@debian.org> To: YunQiang Su <wzssyqa@gmail.com>, 881845@bugs.debian.org Cc: debian-mips@lists.debian.org, Aron Xu <aron@debian.org>, PozueloEmilio Monfort <pochu@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, James Cowgill <jcowgill@debian.org>, Ivo De Decker <ivodd@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Thu, 27 Sep 2018 04:06:00 +0000

Ximin Luo: > Do you have a link to a more detailed description of the problem, so that the rest of us can understand it? > > For example James in message 29 gave a very detailed summary of other previous problems: > > [29] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881845#29 > > Nobody in this thread has stated what the supposed problem actually is with these Cavium/Octeon machines. FYI the builds failed recently on eberlin and manda-03, and has failed in the past on aql-01. These are all octeon, and the other mips64el buildd sil-01 is also octeon. So it seems all our buildds are affected by the bug. So the blacklist approach won't even work. > Oh I take that back, it seems aql-01 and manda-01,02 are not octeon, I had previously assumed all the x-{01..03} machines would be the same. Still, please give us a link to the description of the problem. X > Also unless I can understand the problem, I don't feel happy using the blacklist as a temporary solution, even if it was going to work. > > X > > YunQiang Su: >> It is still about llvm+octeon problem. >> >> Maybe we can ask pin rustc on Loongson machines. >> Ximin Luo <infinity0@debian.org> 于2018年9月24日周一 上午2:21写道： >>> >>> Aron Xu: >>>> [..] >>>>> >>>>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. >>>>> >>>>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. >>>>> >>>> >>>> Will do that and see if we can get the issue either fixed or have a >>>> blacklist placed at the same time. >>>> >>> >>> I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: >>> >>> https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 >>> >>> test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds >>> test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds >>> test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds >>> test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds >>> E: Build killed with signal TERM after 150 minutes of inactivity >>> >>> I still think we should just RM rustc on mips64el. >>> >>> X >>> >>> -- >>> GPG: ed25519/56034877E1F87C35 >>> GPG: rsa4096/1318EFAC5FBBDBCE >>> https://github.com/infinity0/pubkeys.git >>> >> >> > > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Fri, 28 Sep 2018 03:09:03 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Fri, 28 Sep 2018 03:09:03 GMT) (full text, mbox, link).

Message #183 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: infinity0@debian.org Cc: 881845@bugs.debian.org, debian-mips@lists.debian.org, Aron Xu <aron@debian.org>, PozueloEmilio Monfort <pochu@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, James Cowgill <jcowgill@debian.org>, Ivo De Decker <ivodd@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Fri, 28 Sep 2018 11:05:37 +0800

Ximin Luo <infinity0@debian.org> 于2018年9月27日周四 下午12:06写道： > > Ximin Luo: > > Do you have a link to a more detailed description of the problem, so that the rest of us can understand it? > > > > For example James in message 29 gave a very detailed summary of other previous problems: > > > > [29] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881845#29 > > > > Nobody in this thread has stated what the supposed problem actually is with these Cavium/Octeon machines. FYI the builds failed recently on eberlin and manda-03, and has failed in the past on aql-01. These are all octeon, and the other mips64el buildd sil-01 is also octeon. So it seems all our buildds are affected by the bug. So the blacklist approach won't even work. > > > > Oh I take that back, it seems aql-01 and manda-01,02 are not octeon, I had previously assumed all the x-{01..03} machines would be the same. > > Still, please give us a link to the description of the problem. I cannot remember clear. It seems that no branch instruction can be in ll/sc pair on Octeon, while llvm does generate code like this. Loongson has no this problem. anyway, we should patch llvm. > > X > > > Also unless I can understand the problem, I don't feel happy using the blacklist as a temporary solution, even if it was going to work. > > > > X > > > > YunQiang Su: > >> It is still about llvm+octeon problem. > >> > >> Maybe we can ask pin rustc on Loongson machines. > >> Ximin Luo <infinity0@debian.org> 于2018年9月24日周一 上午2:21写道： > >>> > >>> Aron Xu: > >>>> [..] > >>>>> > >>>>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > >>>>> > >>>>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > >>>>> > >>>> > >>>> Will do that and see if we can get the issue either fixed or have a > >>>> blacklist placed at the same time. > >>>> > >>> > >>> I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: > >>> > >>> https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 > >>> > >>> test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds > >>> test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds > >>> test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds > >>> test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds > >>> E: Build killed with signal TERM after 150 minutes of inactivity > >>> > >>> I still think we should just RM rustc on mips64el. > >>> > >>> X > >>> > >>> -- > >>> GPG: ed25519/56034877E1F87C35 > >>> GPG: rsa4096/1318EFAC5FBBDBCE > >>> https://github.com/infinity0/pubkeys.git > >>> > >> > >> > > > > > > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > https://github.com/infinity0/pubkeys.git -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Fri, 28 Sep 2018 09:39:02 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Fri, 28 Sep 2018 09:39:03 GMT) (full text, mbox, link).

Message #188 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: infinity0@debian.org Cc: 881845@bugs.debian.org, debian-mips@lists.debian.org, Aron Xu <aron@debian.org>, PozueloEmilio Monfort <pochu@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, James Cowgill <jcowgill@debian.org>, Ivo De Decker <ivodd@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Fri, 28 Sep 2018 17:35:31 +0800

https://bugs.llvm.org/show_bug.cgi?id=32020 YunQiang Su <wzssyqa@gmail.com> 于2018年9月28日周五 上午11:05写道： > > Ximin Luo <infinity0@debian.org> 于2018年9月27日周四 下午12:06写道： > > > > Ximin Luo: > > > Do you have a link to a more detailed description of the problem, so that the rest of us can understand it? > > > > > > For example James in message 29 gave a very detailed summary of other previous problems: > > > > > > [29] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881845#29 > > > > > > Nobody in this thread has stated what the supposed problem actually is with these Cavium/Octeon machines. FYI the builds failed recently on eberlin and manda-03, and has failed in the past on aql-01. These are all octeon, and the other mips64el buildd sil-01 is also octeon. So it seems all our buildds are affected by the bug. So the blacklist approach won't even work. > > > > > > > Oh I take that back, it seems aql-01 and manda-01,02 are not octeon, I had previously assumed all the x-{01..03} machines would be the same. > > > > Still, please give us a link to the description of the problem. > > I cannot remember clear. > It seems that no branch instruction can be in ll/sc pair on Octeon, > while llvm does generate code like this. > > Loongson has no this problem. anyway, we should patch llvm. > > > > > > X > > > > > Also unless I can understand the problem, I don't feel happy using the blacklist as a temporary solution, even if it was going to work. > > > > > > X > > > > > > YunQiang Su: > > >> It is still about llvm+octeon problem. > > >> > > >> Maybe we can ask pin rustc on Loongson machines. > > >> Ximin Luo <infinity0@debian.org> 于2018年9月24日周一 上午2:21写道： > > >>> > > >>> Aron Xu: > > >>>> [..] > > >>>>> > > >>>>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > > >>>>> > > >>>>> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > > >>>>> > > >>>> > > >>>> Will do that and see if we can get the issue either fixed or have a > > >>>> blacklist placed at the same time. > > >>>> > > >>> > > >>> I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: > > >>> > > >>> https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 > > >>> > > >>> test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds > > >>> test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds > > >>> test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds > > >>> test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds > > >>> E: Build killed with signal TERM after 150 minutes of inactivity > > >>> > > >>> I still think we should just RM rustc on mips64el. > > >>> > > >>> X > > >>> > > >>> -- > > >>> GPG: ed25519/56034877E1F87C35 > > >>> GPG: rsa4096/1318EFAC5FBBDBCE > > >>> https://github.com/infinity0/pubkeys.git > > >>> > > >> > > >> > > > > > > > > > > > > -- > > GPG: ed25519/56034877E1F87C35 > > GPG: rsa4096/1318EFAC5FBBDBCE > > https://github.com/infinity0/pubkeys.git > > > > -- > YunQiang Su -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 02 Oct 2018 14:51:02 GMT) (full text, mbox, link).

Acknowledgement sent to YunQiang Su <wzssyqa@gmail.com> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 02 Oct 2018 14:51:03 GMT) (full text, mbox, link).

Message #193 received at 881845@bugs.debian.org (full text, mbox, reply):

From: YunQiang Su <wzssyqa@gmail.com> To: infinity0@debian.org Cc: Aron Xu <aron@debian.org>, 881845@bugs.debian.org, PozueloEmilio Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 2 Oct 2018 22:48:08 +0800

this problem has been fixed on upstream. https://reviews.llvm.org/rL336328 llvm-6 seems still have this problem, while I guess llvm 7 should be OK now. YunQiang Su <wzssyqa@gmail.com> 于2018年9月27日周四 上午9:33写道： > > It is still about llvm+octeon problem. > > Maybe we can ask pin rustc on Loongson machines. > Ximin Luo <infinity0@debian.org> 于2018年9月24日周一 上午2:21写道： > > > > Aron Xu: > > > [..] > > >> > > >> Aron, the next version 1.27.1 is already in binary-NEW so the same issue will block testing migration again, when that gets accepted. > > >> > > >> Earlier you said "Binary only upload from porter is allowed [..]" but I am not sure the other porters have access to a loongson-3a box. Will you continue to run builds of new rustc versions on your box? I think that is the key point here. > > >> > > > > > > Will do that and see if we can get the issue either fixed or have a > > > blacklist placed at the same time. > > > > > > > I have just uploaded 1.29.0 to unstable. It will need manual building with a non-buggy mips machine, to unblock us for Debian Testing. The previous build 1.29.0+dfsg1-1~exp1 failed due to hanging atomic tests: > > > > https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=mips64el&ver=1.29.0%2Bdfsg1-1%7Eexp1&stamp=1537686627&raw=0 > > > > test sync.rs - sync::Arc (line 124) ... test sync.rs - sync::Arc (line 124) has been running for over 60 seconds > > test sync.rs - sync::Arc<T>::downgrade (line 418) ... test sync.rs - sync::Arc<T>::downgrade (line 418) has been running for over 60 seconds > > test sync.rs - sync::Arc<T>::get_mut (line 856) ... test sync.rs - sync::Arc<T>::get_mut (line 856) has been running for over 60 seconds > > test sync.rs - sync::Arc<T>::make_mut (line 769) ... test sync.rs - sync::Arc<T>::make_mut (line 769) has been running for over 60 seconds > > E: Build killed with signal TERM after 150 minutes of inactivity > > > > I still think we should just RM rustc on mips64el. > > > > X > > > > -- > > GPG: ed25519/56034877E1F87C35 > > GPG: rsa4096/1318EFAC5FBBDBCE > > https://github.com/infinity0/pubkeys.git > > > > > -- > YunQiang Su -- YunQiang Su

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 02 Oct 2018 14:51:04 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 02 Oct 2018 14:51:05 GMT) (full text, mbox, link).

Message #198 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: YunQiang Su <wzssyqa@gmail.com>, infinity0@debian.org Cc: Aron Xu <aron@debian.org>, 881845@bugs.debian.org, PozueloEmilio Monfort <pochu@debian.org>, debian-mips@lists.debian.org, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 2 Oct 2018 16:50:23 +0200

Hi YunQiang! On 10/2/18 4:48 PM, YunQiang Su wrote: > this problem has been fixed on upstream. > > https://reviews.llvm.org/rL336328 > > llvm-6 seems still have this problem, while I guess llvm 7 should be OK now. Can you open bug reports against llvm-toolchain-6.0 and llvm-toolchain-7 to make sure, the fix gets backported? Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 02 Oct 2018 14:57:02 GMT) (full text, mbox, link).

Acknowledgement sent to Sylvestre Ledru <sylvestre@debian.org> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 02 Oct 2018 14:57:02 GMT) (full text, mbox, link).

Message #203 received at 881845@bugs.debian.org (full text, mbox, reply):

From: Sylvestre Ledru <sylvestre@debian.org> To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, 881845@bugs.debian.org, YunQiang Su <wzssyqa@gmail.com>, infinity0@debian.org Cc: PozueloEmilio Monfort <pochu@debian.org>, debian-mips@lists.debian.org, Aron Xu <aron@debian.org>, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures Date: Tue, 2 Oct 2018 16:53:53 +0200

Le 02/10/2018 à 16:50, John Paul Adrian Glaubitz a écrit : > Hi YunQiang! > > On 10/2/18 4:48 PM, YunQiang Su wrote: >> this problem has been fixed on upstream. >> >> https://reviews.llvm.org/rL336328 >> >> llvm-6 seems still have this problem, while I guess llvm 7 should be OK now. > > Can you open bug reports against llvm-toolchain-6.0 and llvm-toolchain-7 to > make sure, the fix gets backported? I would prefer that rustc uses llvm 7 instead of 6. Cheers, Sylvestre

Information forwarded to debian-bugs-dist@lists.debian.org, Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> :

Bug#881845 ; Package src:rustc . (Tue, 02 Oct 2018 14:57:04 GMT) (full text, mbox, link).

Acknowledgement sent to John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> :

Extra info received and forwarded to list. Copy sent to Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org> . (Tue, 02 Oct 2018 14:57:04 GMT) (full text, mbox, link).

Message #208 received at 881845@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> To: Sylvestre Ledru <sylvestre@debian.org>, 881845@bugs.debian.org, YunQiang Su <wzssyqa@gmail.com>, infinity0@debian.org Cc: PozueloEmilio Monfort <pochu@debian.org>, debian-mips@lists.debian.org, Aron Xu <aron@debian.org>, James Cowgill <jcowgill@debian.org> Subject: Re: [Pkg-rust-maintainers] Bug#881845: Bug#