unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sree Harsha Totakura <sreeharsha@totakura.in>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNUnet build failure on mips64el
Date: Sat, 22 Feb 2014 00:33:01 +0100	[thread overview]
Message-ID: <5307E22D.2040305@totakura.in> (raw)
In-Reply-To: <87d2igiit6.fsf@gnu.org>

On 02/21/2014 04:31 PM, Ludovic Courtès wrote:
> On the GNUnet side, it would be great if the tests were less timing sensitive.

We faced these problems earlier when we added Sheevaplug and RasberryPi
into our buildbots.  Unfortunately, since we are having a network
application, the timeouts are necessary.

We can try increasing the timeouts but that makes the test runs long if
a testcase were to fail genuinely.  Guess we'll have to come up with
some automated measurement for timeouts depending on the host
configuration.  I just don't know how; any ideas?

Sree

  parent reply	other threads:[~2014-02-21 23:33 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
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       ` Sree Harsha Totakura [this message]
2014-02-21 12:54 ` GNUnet build failure on mips64el 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

  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=5307E22D.2040305@totakura.in \
    --to=sreeharsha@totakura.in \
    --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 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).