From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#21620: tests/mpz/reuse intermittently fails on armhf-linux-gnu Date: Wed, 07 Oct 2015 22:32:43 +0200 Message-ID: <87a8ru5sic.fsf@gnu.org> References: <87mvvxuxoo.fsf@gnu.org> <868u7gb1s5.fsf@shell.gmplib.org> <87d1wsm0jo.fsf@gnu.org> <87y4ffsa3y.fsf@netris.org> <87egh7b0p0.fsf@gnu.org> <87r3l6onje.fsf@netris.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]:44970) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjvOb-0005WZ-OL for bug-guix@gnu.org; Wed, 07 Oct 2015 16:33:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjvOY-0007ea-FY for bug-guix@gnu.org; Wed, 07 Oct 2015 16:33:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42117) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjvOY-0007eW-Bu for bug-guix@gnu.org; Wed, 07 Oct 2015 16:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1ZjvOY-0002ds-2s for bug-guix@gnu.org; Wed, 07 Oct 2015 16:33:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r3l6onje.fsf@netris.org> (Mark H. Weaver's message of "Wed, 07 Oct 2015 08:45:09 -0400") 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: Mark H Weaver Cc: 21620@debbugs.gnu.org, Andreas Enge Mark H Weaver skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Mark H Weaver skribis: >> >>> 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? >> >> Yes, it was on enge.fr. Could you try on your Novena? > > When used as a build slave, the Novena is prone to overheating. Do you think it=E2=80=99s a likely problem? Andreas, could you try again on your Novena with 2 cores turned off? Thanks, Ludo=E2=80=99.