From: Leo Famulari <leo@famulari.name>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: 22558@debbugs.gnu.org
Subject: bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra
Date: Fri, 5 Feb 2016 13:58:09 -0500 [thread overview]
Message-ID: <20160205185809.GA18204@jasmine> (raw)
In-Reply-To: <e112c8428d525be86ac8ed2d20aa9e5f@openmailbox.org>
On Fri, Feb 05, 2016 at 09:25:10AM -0600, Eric Bavier wrote:
> >> * With 14 test failures. This happened at least twice, on
> >> hydra.gnunet.org.
> >
> >Eric Bavier reported on #guix that it failed to build on his machine
> >twice in a row, with 14 test failures.
>
> I used 'git bisect' on the gnupg repository to narrow the failures down.
> Commit ee87c653bf is the commit that introduces the failures.
>
> Knowing this however doesn't explain why Ludo was not able to reproduce on
> his machine or why Hydra was eventually able to build it successfully.
It fails on my x86_64 machine as well, also with those 14 test failures.
Will somebody for whom it builds successfully see if it builds
reproducibly on their machine?
>
> --
> `~Eric
>
>
>
next prev parent reply other threads:[~2016-02-05 18:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 15:28 Gnupg 2.1.11 Andreas Enge
2016-02-04 16:58 ` Ludovic Courtès
2016-02-04 19:36 ` Andreas Enge
2016-02-04 20:59 ` Mark H Weaver
2016-02-05 15:25 ` bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra Eric Bavier
2016-02-05 18:58 ` Leo Famulari [this message]
2016-02-07 20:50 ` Ludovic Courtès
2016-02-12 23:22 ` Mark H Weaver
2016-02-13 0:12 ` Leo Famulari
2016-02-13 2:13 ` Mark H Weaver
2016-02-13 4:02 ` Eric Bavier
2016-02-13 7:41 ` Leo Famulari
2016-02-13 7:46 ` Leo Famulari
2016-02-13 14:36 ` Mark H Weaver
2016-02-06 16:52 ` Gnupg 2.1.11 Alex Vong
2016-02-06 17:44 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2016-02-04 19:58 bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra Mark H Weaver
2016-02-04 20:22 ` Mark H Weaver
2016-02-04 20:40 ` Mark H Weaver
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=20160205185809.GA18204@jasmine \
--to=leo@famulari.name \
--cc=22558@debbugs.gnu.org \
--cc=ericbavier@openmailbox.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.