From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: guix-devel@gnu.org, 19805@debbugs.gnu.org
Subject: Re: bug#19805: Numpy failures
Date: Tue, 10 Feb 2015 00:07:07 +0100 [thread overview]
Message-ID: <87zj8m7kh0.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPOfkGiy2GTutqcW_s5p+Cgpe=hF_P0pxpuT6PxrPP5FvQ@mail.gmail.com> (Federico Beffa's message of "Mon, 9 Feb 2015 09:30:16 +0100")
Federico Beffa <beffa@ieee.org> skribis:
> Andreas Enge <andreas@enge.fr> writes:
>
>> python-numpy-bootstrap currently fails its tests on hydra, which entails a
>> bunch of other failures. On my own x86_64 machines, the build succeeds,
>> however.
>
> We believe the reason being the fact that hydra doesn't handle the flag
> '#:substitutable?' properly. As a result we have the following
> situation:
>
> 1. hydra builds a version of ATLAS optimized for its CPU locally.
>
> 2. 'python-numpy-bootstrap' and co., on some architectures, probably get
> an incompatible version of ATLAS and therefore fail to pass some tests.
>
> You can check in the build log of 'python-numpy-bootstrap' that ATLAS,
> despite the flas, is substituted (no local build on the slave).
Oh. Actually, slaves do not use substitutes at all, but they receive
missing store items from hydra.gnu.org when builds are offloaded. So I
suppose they receive something built on hydra.gnu.org, which may be
incompatible.
> At some point we should fix the support for '#:substitutable?' on hydra
That probably means that #:substitutable? should be propagated–i.e.,
that anything depending on ATLAS should not be substituted.
Thanks for investigating!
Ludo’.
next prev parent reply other threads:[~2015-02-09 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 16:41 Numpy failures Andreas Enge
2015-02-09 8:30 ` Federico Beffa
2015-02-09 23:07 ` bug#19805: " Ludovic Courtès
2015-02-09 23:07 ` Ludovic Courtès [this message]
2015-02-10 13:20 ` Federico Beffa
2015-02-10 13:20 ` Federico Beffa
2015-02-10 13:52 ` Mark H Weaver
2015-02-10 14:41 ` Ludovic Courtès
2015-02-10 14:41 ` Ludovic Courtès
2015-09-11 19:40 ` Ludovic Courtès
2015-02-10 13:52 ` 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=87zj8m7kh0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19805@debbugs.gnu.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.