From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH] gnu: Add dlib.
Date: Wed, 31 Aug 2016 15:09:08 -0400 [thread overview]
Message-ID: <20160831190908.GD12396@jasmine> (raw)
In-Reply-To: <87mvjuz5ae.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me>
On Tue, Aug 30, 2016 at 03:43:05PM +0100, Marius Bakke wrote:
> Shogun failed to build in this run. I don't have time to investigate
> further, so picking the OpenBLAS update is not very appealing.
>
> Instead I opted to disable the test that fails with lapack (and without,
> on Hydra), since it's one specific openblas operation that is not unique
> to dlib. I think it's an acceptable tradeoff, to give users the full
> dlib functionality, and have the segfault "sort itself" when
> core-updates lands in master.
Okay, this sounds fine to me.
> Below is a patch which disables these tests (and the above segfault) for
> 19.1, rather than backporting the patches from dlib master branch.
>
> One note about the patch: I could not figure out how to pass the list of
> tests as arguments to `substitute*`, so currently it calls `substitute*`
> for each of them. Any tips to prevent this?
Not from me — Calling all seasoned Schemers to thread :) If nobody
replies I will say this solution is fine.
Changing the subject, you could disable the tests per-architecture. Look
for uses of current-target-system and current-system for usage examples.
But this is not absolutely required, IMO.
> It also no longer builds the main application twice for tests.
Thank you :)
next prev parent reply other threads:[~2016-08-31 19:09 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
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 [this message]
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=20160831190908.GD12396@jasmine \
--to=leo@famulari.name \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--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).