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: Sat, 13 Dec 2014 14:09:14 -0500	[thread overview]
Message-ID: <87vblfqsdh.fsf@netris.org> (raw)
In-Reply-To: <CAKrPhPO0-HLTX_-Y7Fw1jo+7nX1J5n-WYA=kZT5Ce__ughqMSQ@mail.gmail.com> (Federico Beffa's message of "Sat, 13 Dec 2014 18:35:08 +0100")

Federico Beffa <beffa@ieee.org> writes:

> On Thu, Dec 11, 2014 at 2:20 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Check if that flag has an effect at all.  For instance,
>> Automake-generated makefiles have supported parallel test suites for
>> not-too-long (a couple of years maybe) and even there it’s optional.
>> Hand-written build systems often run tests sequentially.
>
> I think you are right that the flag does not have any effect here.
>
> I've now identified the failing test. From the comment in the test
> procedure it appears that it has to do with memory
>
> https://github.com/numpy/numpy/issues/4442

Thanks for looking into it!

> Could I know the specs of the hydra (virtual?) machine running the
> code? I may reduce the size of the test matrix, or skip the test
> altogether.

The builds don't happen on hydra.gnu.org itself, they happen on its
build slaves, of which there are several.  Anyway, the question is not
relevant, because we want users to be able to build packages on their
own machines.  We'll just have to use our own judgment about what the
minimum requirements should be to build this package.

    Thanks!
      Mark

      reply	other threads:[~2014-12-13 19:09 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
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 [this message]

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=87vblfqsdh.fsf@netris.org \
    --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.