From: Leo Famulari <leo@famulari.name>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: 22558-done@debbugs.gnu.org
Subject: bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra
Date: Sat, 13 Feb 2016 02:41:18 -0500 [thread overview]
Message-ID: <20160213074118.GA24222@jasmine> (raw)
In-Reply-To: <20160212220232.2b89e386@openmailbox.org>
On Fri, Feb 12, 2016 at 10:02:32PM -0600, Eric Bavier wrote:
> On Fri, 12 Feb 2016 21:13:55 -0500
> Mark H Weaver <mhw@netris.org> wrote:
>
> > Leo Famulari <leo@famulari.name> writes:
> >
> > > On Fri, Feb 12, 2016 at 06:22:46PM -0500, Mark H Weaver wrote:
> > >> ludo@gnu.org (Ludovic Courtès) writes:
> > >>
> > >> > Eric Bavier <ericbavier@openmailbox.org> skribis:
> > >> >
> > >> >>> > * 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.
> > >> >
> > >> > Thanks for digging! Could you report it upstream?
> > >>
> > >> I reported it upstream, and now they have a fix in their repo.
> > >> I've attached a patch to Guix which adds this upstream patch.
> > >>
> > >> Eric, would you be willing to test it and see if it fixes the problem
> > >> for you?
> > >
> > > I'm not Eric, but with this patch, I can successfully build on the
> > > machine that was previously exhibiting the failures.
> >
> > Thanks! I went ahead and pushed this to master, commit 3a7261bf96.
> > I'm closing this bug now.
>
> I realize I'm a bit late, but I just wanted to let you know that this
> appears to fix the gnupg-2.1.11 build for me too:
>
> @ build-succeeded /gnu/store/qyjrqxnrka55p5g5vh1p80ac1rxn5nfm-gnupg-2.1.11.drv -
> /gnu/store/w6fbikpwzpjkwvy6z1hwbszq0x83yspv-gnupg-2.1.11
>
> But I had to add "#:use-module (gnu packages)" to the
> gnu/packages/gnupg.scm before it would build, otherwise "could not
> find symbol search-path".
Weird, that did not happen to me when building from 3a7261bf96b2 on
x86_64 with a recent guix-daemon.
next prev parent reply other threads:[~2016-02-13 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160204152848.GA4379@debian>
[not found] ` <87r3gs9zvf.fsf@gnu.org>
[not found] ` <20160204193649.GA8785@debian>
[not found] ` <87d1scxkd6.fsf@netris.org>
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
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 [this message]
2016-02-13 7:46 ` Leo Famulari
2016-02-13 14:36 ` Mark H Weaver
2016-02-04 19:58 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
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=20160213074118.GA24222@jasmine \
--to=leo@famulari.name \
--cc=22558-done@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 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).