From: ludo@gnu.org (Ludovic Courtès)
To: "Jan Synáček" <jan.synacek@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Test failure when building libarchive-3.1.2
Date: Sat, 14 Nov 2015 12:40:20 +0100 [thread overview]
Message-ID: <87h9koyfkr.fsf@gnu.org> (raw)
In-Reply-To: <CACA+5f3BPcpP=jnW2ECAi8oW53ye3hGij_3c0o2DO7beL88Z8Q@mail.gmail.com> ("Jan \=\?utf-8\?B\?U3luw6HEjWVrIidz\?\= message of "Fri, 13 Nov 2015 12:33:32 +0100")
Jan Synáček <jan.synacek@gmail.com> skribis:
> Reference files will be read from:
> /tmp/nix-build-libarchive-3.1.2.drv-0/libarchive-3.1.2/tar/test
> Running tests on:
> "/tmp/nix-build-libarchive-3.1.2.drv-0/libarchive-3.1.2/./bsdtar"
> Exercising: bsdtar 3.1.2 - libarchive 3.1.2
[...]
> 17: test_option_b FAIL
Ricardo reported the same issue a while back:
https://lists.gnu.org/archive/html/guix-devel/2015-03/msg00182.html
What platform is this on, i686?
It would be nice to see if this systematically fails. If it is
non-deterministic, we should build it with --keep-failed until it fails
(removing successful builds with ‘guix gc -d’), collect useful info from
the build tree, and debug.
(You can also work around it by enabling substitutes since Hydra had no
problems building it.)
Ludo’.
next prev parent reply other threads:[~2015-11-14 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 11:33 Test failure when building libarchive-3.1.2 Jan Synáček
2015-11-14 11:40 ` Ludovic Courtès [this message]
2015-11-14 12:47 ` Jan Synáček
2015-11-20 13:51 ` Ludovic Courtès
2015-11-20 14:10 ` Jan Synáček
2015-11-20 22:47 ` Ludovic Courtès
2015-11-21 7:58 ` Jan Synáček
2015-11-21 10:17 ` Ludovic Courtès
2015-11-20 13:44 ` Jan Synáček
2015-11-20 13:48 ` Jan Synáček
2015-11-20 22:45 ` Ludovic Courtès
2015-11-21 15:38 ` guix refresh -l Ludovic Courtès
2015-11-21 16:06 ` Mathieu Lirzin
2015-11-21 20:31 ` Jan Synáček
2015-12-09 22:55 ` Test failure when building libarchive-3.1.2 Ludovic Courtès
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=87h9koyfkr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jan.synacek@gmail.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).