From: ludo@gnu.org (Ludovic Courtès)
To: Jeremy Robst <jpro@bas.ac.uk>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add hdf4
Date: Fri, 03 Jun 2016 10:37:49 +0200 [thread overview]
Message-ID: <87lh2m3bxe.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1606021549370.16068@jpro.nerc-bas.ac.uk> (Jeremy Robst's message of "Thu, 2 Jun 2016 15:58:12 +0100 (BST)")
Hello,
Jeremy Robst <jpro@bas.ac.uk> skribis:
>>> Any ideas?
>>
>> I get the same failures intermittently. Other times the build passes.
>
> Yes, I've built it many times over the past few days - sometimes I get
> a failure, other times it builds ok, like you. If I do
>
> ./pre-inst-env guix gc
> ./pre-inst-env guix build hdf4
Instead, you can run:
./pre-inst-env guix build --check hdf4
> Looking at the HDF code it's doing things with the maximum number of
> open files - is there anything guix does when it's creating the
> restricting environment for the build user that would limit the number
> of open files ?
It does not use ‘setrlimit’, which means it inherits the limits of its
parent process.
There was a problem on the maximum number of processes for people
running guix-daemon from systemd, which commit
f489ce3c9343e3ba9927645d11fcb91bb69f0fa7 addressed.
But anyway, I hit the problem on GuixSD, so it’s not systemd-related.
It might be worth trying:
#:parallel-tests? #f
though I suspect it’s a per-process limit that we’re hitting, not a
global limit.
Next step would be to ask the HDF4 developers. :-)
> libhdf4.settings includes the build user and the details of the build
> host as well as the build time. This file is included in the final
> build. I patched configure to set the build time to the epoch, taken
> from the HDF5 patch.
Clearing the build time is definitely necessary.
> However I also changed the libhdf4.settings to remove details of the
> build user and build host since I was aiming for reproducibilty across
> builds across machines. E.g I happen to always have built it with the
> user guixbuild00, but if I was building 2 or more things in parallel
> then it might get built with guixbuild01 and I thought this would then
> show us as a different build (since the username would be in
> libhdf4.settings in the file output). Is that right or am I
> misunderstanding something ?
You are right, the user name could differ, so it’s best to patch it if
it gets embedded in the end.
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-06-03 8:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 17:22 [PATCH] gnu: Add hdf4 Jeremy Robst
2016-05-23 18:17 ` Leo Famulari
2016-05-24 13:20 ` Jeremy Robst
2016-05-24 19:06 ` Eric Bavier
2016-05-25 17:42 ` Jeremy Robst
2016-05-27 17:19 ` Leo Famulari
2016-05-28 14:32 ` Ludovic Courtès
2016-05-29 17:36 ` Jeremy Robst
2016-05-29 22:07 ` Ludovic Courtès
2016-06-02 14:43 ` Eric Bavier
2016-06-02 14:58 ` Jeremy Robst
2016-06-03 8:37 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-11 8:57 Thomas Danckaert
2016-10-12 12:54 ` Ludovic Courtès
2016-10-12 18:50 ` Thomas Danckaert
2016-10-12 20:28 ` Ludovic Courtès
2016-10-14 8:11 ` Andreas Enge
2016-10-14 11:13 ` Thomas Danckaert
[not found] ` <20161014.110029.603260973900204345.post@thomasdanckaert.be>
2016-10-16 15:05 ` Andreas Enge
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=87lh2m3bxe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jpro@bas.ac.uk \
/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.