unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 21620@debbugs.gnu.org, Andreas Enge <andreas.enge@inria.fr>
Subject: bug#21620: tests/mpz/reuse intermittently fails on armhf-linux-gnu
Date: Thu, 08 Oct 2015 20:53:22 -0400	[thread overview]
Message-ID: <87a8rsooal.fsf@netris.org> (raw)
In-Reply-To: <20151008190754.GA6984@debian> (Andreas Enge's message of "Thu, 8 Oct 2015 21:07:54 +0200")

Andreas Enge <andreas@enge.fr> writes:

> On Wed, Oct 07, 2015 at 10:32:43PM +0200, Ludovic Courtès wrote:
>> Do you think it’s a likely problem?  Andreas, could you try again on
>> your Novena with 2 cores turned off?
>
> I have trouble believing the explanation of overheating. The gmp test
> suite is carried out sequentially (they are not yet using the parallel
> test harness of the autotools). So one could only imagine that the build
> itself was faulty, but should then the test not fail consistently afterwards?
> If I understood correctly, you used one build and ran the same test
> over and over again. On the other hand, since the machine also serves as a
> build machine, it is possible that some other package was built at the same
> time as the tests were carried out, which may have contributed to heating.

Exactly.

FWIW, I looked through my archive of build failure logs, and found that
the same 'reuse' test failed around September 10th on hydra-slave1, the
Novena donated by Steve Sprang.  I know that on a few occasions I forgot
to disable 2/4 cores, and that might have been one of those times.
Actually, right now hydra-slave1 has all 4 cores enabled and it seems to
be doing alright.  I also built 'gmp' again on it with 4 cores, and it
passed the 'reuse' test.  I aborted the build after that test passed,
and left the build directory in /tmp, so we could try running the
'reuse' test repeatedly if desired.

      Mark

  reply	other threads:[~2015-10-09  0:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 14:33 bug#21620: GMP 6.0.0a intermittent test failure on armhf Ludovic Courtès
2015-10-05 15:44 ` bug#21620: tests/mpz/reuse intermittently fails on armhf-linux-gnu Ludovic Courtès
2015-10-06 12:48   ` Torbjörn Granlund
2015-10-06 16:20     ` Ludovic Courtès
2015-10-07  2:09       ` Mark H Weaver
2015-10-07  7:24         ` Ludovic Courtès
2015-10-07 12:45           ` Mark H Weaver
2015-10-07 13:08             ` Andreas Enge
2015-10-07 13:39               ` Mark H Weaver
2015-10-07 20:32             ` Ludovic Courtès
2015-10-08 19:07               ` Andreas Enge
2015-10-09  0:53                 ` Mark H Weaver [this message]
2015-10-09  8:27                 ` Ludovic Courtès
2015-11-20 14:53                   ` Ludovic Courtès
2016-06-02 19:43                     ` Ludovic Courtès
2015-10-07 14:28       ` Torbjörn Granlund

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8rsooal.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=21620@debbugs.gnu.org \
    --cc=andreas.enge@inria.fr \
    --cc=andreas@enge.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).