Re: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures
- 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
- From: Ximin Luo <infinity0@debian.org>
- Date: Sun, 23 Sep 2018 17:57:00 +0000
- Message-id: <[🔎] aa09158d-b537-89c9-076d-af231b6ed062@debian.org>
- In-reply-to: <CAMr=8w4hef-GyDrZaX_DGSALiAgN+XKnVRps3tSdA-kjeqmj_A@mail.gmail.com>
- References: <f4a9abc3-45a0-73be-4155-f0481de404d6@debian.org> <b55cde1e-be84-8920-9af0-28afaca10b73@debian.org> <e4410f6a-e0c1-055c-b75b-d0529e5ebb94@debian.org> <93492683-c48e-ee22-b57d-5cbe991d0526@debian.org> <b558dd41-8d6f-bd09-ce32-6e8da145db36@physik.fu-berlin.de> <7988b886-90ab-29ea-c4ea-d5ad719e1340@debian.org> <40b05763-e033-519b-513e-f18085a1a527@debian.org> <CAMr=8w5D1E2-PubE5oRk6goDC=xCjMmVgTAR6T0U3sCbwv4Y-g@mail.gmail.com> <b83f57ad-25d9-d4d7-e746-c68019be1fde@physik.fu-berlin.de> <CAMr=8w4hgR6pxO2+6PiMtrr9kGm_u_vgj2G87T3hhT9-aK6kLg@mail.gmail.com> <e41f427c-abaf-3439-bcd1-4f6e8a324f6c@physik.fu-berlin.de> <CAMr=8w7ActcOgc6U67ZOXJ1+9OfaFw3Kp9AQtBeF57CoNbi31w@mail.gmail.com> <151076701519.20906.15281420312233839245.reportbug@tatooine> <2d3a7b48-3e22-accd-5f73-52fc4bf5306a@physik.fu-berlin.de> <6097be0f-3ab8-f964-151f-66cc07a6acf6@debian.org> <151076701519.20906.15281420312233839245.reportbug@tatooine> <CAMr=8w4hef-GyDrZaX_DGSALiAgN+XKnVRps3tSdA-kjeqmj_A@mail.gmail.com>
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
Reply to: