From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH] gnu: Add dlib.
Date: Wed, 17 Aug 2016 15:01:24 +1000 [thread overview]
Message-ID: <4e2f9e6e-e232-9f49-7c25-92a11d3d848a@uq.edu.au> (raw)
In-Reply-To: <d29f34fd-d2b6-26a3-3c3a-1ac35ef59e56@uq.edu.au>
On 17/08/16 13:24, Ben Woodcroft wrote:
>
>
> On 17/08/16 09:45, Leo Famulari wrote:
>> On Wed, Aug 17, 2016 at 09:31:11AM +1000, Ben Woodcroft wrote:
>>>
>>> On 17/08/16 06:47, Leo Famulari wrote:
>>>> On Tue, Aug 16, 2016 at 11:45:16AM +0100, Marius Bakke wrote:
>>>>> I initially made this package on a foreign distro without "lapack" in
>>>>> inputs and have verified that dropping LAPACK makes the tests pass.
>>>>>
>>>>> I also found some other optional dependencies after digging around
>>>>> the
>>>>> source, as well as a recommendation to disable/enable asserts:
>>>>>
>>>>> http://dlib.net/dlib/config.h.html
>>>>>
>>>>> Ben, Leo: Can you try the following patch and see if that works
>>>>> for you?
>>>> Yes, this patch builds for me.
>>> Me too, although it appeared non-deterministic. I'm afraid I haven't
>>> time to
>>> see if this patch is suitable to push just now. Leo?
>> How did it appear non-deterministic to you?
> Just based on guix build --check:
>
> guix build: error: build failed: derivation
> `/gnu/store/sxybcxw64q1ajzq6dysal75ffgq6238i-dlib-19.1.drv' may not be
> deterministic: output
> `/gnu/store/il57dcii4pzii11zlixjjxxxw699bg5x-dlib-19.1' differs
>
> I'm actually not sure, why does it say "may not be deterministic"? If
> it builds twice and the second version is different, doesn't that mean
> it is definitely not deterministic by counter-example, unless there
> has been some leakage into the build container?
>
> I also tried building it with #parallel-build? #f and #parallel-tests?
> #f. It worked in the first round but failed the second.
I wasn't clear here. This was with lapack uncommented out. Subsequently
I tested with both these flags #f and lapack commented out, then it was
deterministic with --rounds=2. Let me know if you want any further
testing done.
next prev parent reply other threads:[~2016-08-17 5:01 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 [this message]
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
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=4e2f9e6e-e232-9f49-7c25-92a11d3d848a@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).