all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNUnet build failure on mips64el
Date: Fri, 21 Feb 2014 16:39:28 +0100	[thread overview]
Message-ID: <20140221153928.GA31681@debian> (raw)
In-Reply-To: <87d2igiit6.fsf@gnu.org>

On Fri, Feb 21, 2014 at 04:31:17PM +0100, Ludovic Courtès wrote:
> > We were discussing this yesterday on the IRC.  It looks like the tests
> > are timing out due to hydra being slow.  I tested this on my machine and
> > 2 other X86_64s and they did well.
> Indeed, it built fine on my x86_64 machine.

The same holds for Qt - its build times out after 2 hours, when it is simply
not finished. Could we raise the timeout on hydra?

Another thing: We have "four cores" (I suppose actually two hyperthreaded
ones) on hydra. On my machine, "top" shows four times 100%. On hydra, I get
the impression that only one core is working. Is this normal (due to outside
load, maybe), or do we need to tweak something?

Andreas

  reply	other threads:[~2014-02-21 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  6:22 GNUnet build failure on mips64el Mark H Weaver
2014-02-21 11:27 ` Andreas Enge
2014-02-21 13:01   ` Sree Harsha Totakura
2014-02-21 15:31     ` Ludovic Courtès
2014-02-21 15:39       ` Andreas Enge [this message]
2014-02-21 17:49         ` Ludovic Courtès
2014-02-21 18:20           ` Andreas Enge
2014-02-25  9:05             ` Andreas Enge
2014-02-27 21:29               ` Build timeout on Hydra Ludovic Courtès
2014-02-21 23:33       ` GNUnet build failure on mips64el Sree Harsha Totakura
2014-02-21 12:54 ` Sree Harsha Totakura
2014-02-21 21:46   ` Mark H Weaver
2014-02-21 23:28     ` Sree Harsha Totakura
2014-02-22  7:44       ` Mark H Weaver
2014-02-22  8:46         ` Sree Harsha Totakura
2014-02-22 11:41           ` Christian Grothoff

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

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

  git send-email \
    --in-reply-to=20140221153928.GA31681@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.