From: Jeremy Robst <jpro@bas.ac.uk>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add hdf4
Date: Thu, 2 Jun 2016 15:58:12 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.20.1606021549370.16068@jpro.nerc-bas.ac.uk> (raw)
In-Reply-To: <22481a77dcf5733b4547f9ecf1a390a3@openmailbox.org>
Hi,
>> 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
it usually (but not always) fails, if I repeat the build it succeeds, then
the only way I can get it to fail again is by doing a gc. I haven't
managed to get the tests to fail building by hand.
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 ?
> Also, I've verified that the part of the patch that touches
> libhdf4.settings.in is not required for build reproducibility.
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.
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 ?
Jeremy
--
jpro@bas.ac.uk | (work) 01223 221402 (fax) 01223 362616
Unix System Administrator - British Antarctic Survey
#include <disclaimer.std>
next prev parent reply other threads:[~2016-06-02 14:58 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 [this message]
2016-06-03 8:37 ` Ludovic Courtès
-- 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=alpine.DEB.2.20.1606021549370.16068@jpro.nerc-bas.ac.uk \
--to=jpro@bas.ac.uk \
--cc=guix-devel@gnu.org \
/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.