From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#21620: tests/mpz/reuse intermittently fails on armhf-linux-gnu Date: Tue, 06 Oct 2015 22:09:21 -0400 Message-ID: <87y4ffsa3y.fsf@netris.org> References: <87mvvxuxoo.fsf@gnu.org> <868u7gb1s5.fsf@shell.gmplib.org> <87d1wsm0jo.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48168) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjeCB-0002Yy-3k for bug-guix@gnu.org; Tue, 06 Oct 2015 22:11:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjeC6-0006AL-OG for bug-guix@gnu.org; Tue, 06 Oct 2015 22:11:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:40409) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjeC6-0006AH-Kr for bug-guix@gnu.org; Tue, 06 Oct 2015 22:11:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1ZjeC6-0003rB-A3 for bug-guix@gnu.org; Tue, 06 Oct 2015 22:11:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87d1wsm0jo.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 06 Oct 2015 18:20:11 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 21620@debbugs.gnu.org, Andreas Enge [removed tg@gmplib.org and gmp-bugs@gmplib.org from the CC list] ludo@gnu.org (Ludovic Court=C3=A8s) writes: > tg@gmplib.org (Torbj=C3=B6rn Granlund) skribis: > >> This is most surely a hardware problem. The most common such problem is >> a bad RAM chip. > > OK, I=E2=80=99ll see if I can reproduce it on another ARMv7 machine and > report back. > > However, the machine in question is a build machine and it would be > surprising for the RAM issue to manifest only for this program. Do we have a record of which build slave performed the failed build? Mark