all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: hydra python2-numpy-1.9.1 failure
Date: Wed, 10 Dec 2014 13:33:21 -0500	[thread overview]
Message-ID: <87lhmf9wy6.fsf@yeeloong.lan> (raw)
In-Reply-To: <CAKrPhPOXodBDqtDTjgxaxB64MkQV3BoJYrQ1bvWzpNe=xEY9ng@mail.gmail.com> (Federico Beffa's message of "Wed, 10 Dec 2014 19:06:16 +0100")

Federico Beffa <beffa@ieee.org> writes:

> I've noticed that on hydra python2-numpy-1.9.1 for x86_64-linux (and
> other architectures) fails to pass the test procedure (really the
> module local version without documentation called
> python2-numpy-bootstrap-1.9.1):
>
> http://hydra.gnu.org/build/172563
>
> So, I've built it locally to investigate and on my machine it builds
> without errors. The hash in the store is the same as on hydra
>
> /gnu/store/wyzv0xw9fi0hks5x1kagy2nl2sykbr7l-python2-numpy-bootstrap-1.9.1
>
> so the inputs should be the same.
>
> I'm at commit 57c3f71632692d1e2e12e5d2db5c2cc4c6e075c9 (of today). The
> only part which is not up to date on my system is the daemon which is
> still from the 0.7 release (back then I've setup an init script to
> start it automatically at boot).
>
> Any hint at what could be going wrong on hydra?

It's not uncommon for some tests to fail occasionally in certain
packages.  Reasons I've seen include: timeouts set too short, race
conditions, randomized tests that fail for some values, and dependencies
on the kernel version and/or configuration.  We've had to debug these
problems on a case-by-case basis.  Sometimes we've disabled the
unreliable tests, or even disabled the entire test suite.

       Mark

  reply	other threads:[~2014-12-10 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 18:06 hydra python2-numpy-1.9.1 failure Federico Beffa
2014-12-10 18:33 ` Mark H Weaver [this message]
2014-12-10 21:19   ` Federico Beffa
2014-12-11  4:19     ` Mark H Weaver
2014-12-11 13:20     ` Ludovic Courtès
2014-12-13 17:35       ` Federico Beffa
2014-12-13 19:09         ` Mark H Weaver

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=87lhmf9wy6.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=beffa@ieee.org \
    --cc=guix-devel@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.