From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Leo Famulari <leo@famulari.name>, Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH] gnu: Add dlib.
Date: Sun, 21 Aug 2016 22:30:09 -0400 [thread overview]
Message-ID: <6004b842-2434-9cdc-7a31-04231eac5941@uq.edu.au> (raw)
In-Reply-To: <20160821201757.GA21038@jasmine>
On 21/08/16 16:17, Leo Famulari wrote:
> On Fri, Aug 19, 2016 at 11:52:37AM +0100, Marius Bakke wrote:
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> I pushed the patch as 5f0ff6a9e. Hopefully dlib is still useful without
>>> lapack. We should really figure out what the issue is and fix it :)
>> I noticed this fails to build on Hydra. What's worse is that the i686,
>> x86_64 and armhf targets fails at completely different things. armhf and
>> i686 exits cleanly after failing 2 and 5 tests respectively, while the
>> x86_64 target seems to get the segfault we saw with lapack in inputs.
>>
>> What should we do? I'd prefer to keep the package so it can easily be
>> tested on various architectures, but can understand if it is reverted.
>> Perhaps we can disable substitutes or tests, to stop bothering Hydra?
>>
>> I'll try reproducing it this weekend on various qemu configurations.
> Let us know about the results of your tests. Then we can decide what to
> do.
Can this be fixed simply by using #parallel-build #f ? Doing so makes it
reproducible for me so arguably we should be doing that anyway, even if
it takes longer to build.
ben
next prev parent reply other threads:[~2016-08-22 2:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 17:15 [PATCH] gnu: Add dlib Marius Bakke
2016-08-14 17:25 ` Leo Famulari
2016-08-14 19:52 ` Marius Bakke
2016-08-15 7:43 ` Alex Kost
2016-08-15 11:51 ` Marius Bakke
2016-08-15 20:15 ` Leo Famulari
2016-08-15 20:29 ` Marius Bakke
2016-08-15 22:28 ` Leo Famulari
2016-08-16 0:15 ` Ben Woodcroft
2016-08-16 10:45 ` Marius Bakke
2016-08-16 20:47 ` Leo Famulari
2016-08-16 23:31 ` Ben Woodcroft
2016-08-16 23:45 ` Leo Famulari
2016-08-17 3:24 ` Ben Woodcroft
2016-08-17 5:01 ` Ben Woodcroft
2016-08-17 14:48 ` Marius Bakke
2016-08-18 20:23 ` Leo Famulari
2016-08-19 10:52 ` Marius Bakke
2016-08-21 20:17 ` Leo Famulari
2016-08-22 2:30 ` Ben Woodcroft [this message]
2016-08-22 12:01 ` Marius Bakke
2016-08-23 18:33 ` Marius Bakke
2016-08-24 10:26 ` Marius Bakke
2016-08-24 17:26 ` Leo Famulari
2016-08-24 19:08 ` Marius Bakke
2016-08-24 22:51 ` Ben Woodcroft
2016-08-30 14:43 ` Marius Bakke
2016-08-31 19:09 ` Leo Famulari
2016-09-09 12:15 ` Marius Bakke
2016-09-10 12:32 ` Marius Bakke
2016-09-10 18:16 ` Leo Famulari
2016-09-13 5:14 ` Leo Famulari
2016-09-13 5:14 ` Leo Famulari
2016-08-18 20:18 ` Leo Famulari
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=6004b842-2434-9cdc-7a31-04231eac5941@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=mbakke@fastmail.com \
/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).