From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: bug#19805: Numpy failures
Date: Tue, 10 Feb 2015 00:07:07 +0100
Message-ID: <87zj8m7kh0.fsf@gnu.org>
References: <20150207164108.GA7946@debian>
	<CAKrPhPOfkGiy2GTutqcW_s5p+Cgpe=hF_P0pxpuT6PxrPP5FvQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46852)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1YKxQC-0000OX-VO
	for guix-devel@gnu.org; Mon, 09 Feb 2015 18:07:18 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1YKxQ7-0005dv-On
	for guix-devel@gnu.org; Mon, 09 Feb 2015 18:07:16 -0500
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37226)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@gnu.org>)
	id 1YKxQ7-0005dp-LL
	for guix-devel@gnu.org; Mon, 09 Feb 2015 18:07:11 -0500
In-Reply-To: <CAKrPhPOfkGiy2GTutqcW_s5p+Cgpe=hF_P0pxpuT6PxrPP5FvQ@mail.gmail.com>
	(Federico Beffa's message of "Mon, 9 Feb 2015 09:30:16 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Federico Beffa <beffa@ieee.org>
Cc: guix-devel@gnu.org, 19805@debbugs.gnu.org

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=E2=80=93i.e.,
that anything depending on ATLAS should not be substituted.

Thanks for investigating!

Ludo=E2=80=99.