From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22826@debbugs.gnu.org
Subject: bug#22826: gnupg test failure
Date: Mon, 29 Feb 2016 16:57:56 -0500 [thread overview]
Message-ID: <87bn6ztc0r.fsf@netris.org> (raw)
In-Reply-To: <87r3fwx27n.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 28 Feb 2016 16:51:40 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Danny Milosavljevic <dannym@scratchpost.org> writes:
>>
>>> gnupg fails its tests:
>>>
>>> ...
>>> note: keeping build directory `/tmp/guix-build-gnupg-2.1.11.drv-0'
>>> builder for `/gnu/store/p91ba6zl4d8gr5ixfqxn8ixhrv13kdv9-gnupg-2.1.11.drv' failed with exit code 1
>>> cannot build derivation `/gnu/store/ixcbdqm2xvclfnz4d25nv53wnp6x7alh-profile.drv': 1 dependencies couldn't be built
>>> cannot build derivation `/gnu/store/904rahmy35wrhsfdb26pcfxyirhbmlnk-system.drv': 1 dependencies couldn't be built
>>> note: keeping build directory `/tmp/guix-build-linux-libre-4.4.3-gnu.tar.xz.drv-0'
>>> guix system: error: build failed: build of `/gnu/store/904rahmy35wrhsfdb26pcfxyirhbmlnk-system.drv' failed
>>>
>>> More details:
>>>
>>> FAIL: gpgtar.test
>>> Test: gpgtar.test
>>> GNUPGHOME=/tmp/guix-build-gnupg-2.1.11.drv-0/gnupg-2.1.11/tests/openpgp
>>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created 2003-12-31
>>> gpgtar: gpg2: "Test two (no pp) <two@example.com>"
>>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created 2003-12-31
>>> gpgtar: gpg2: "Test two (no pp) <two@example.com>"
>>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created 2003-12-31
>>> gpgtar: gpg2: "Test two (no pp) <two@example.com>"
>>> gpgtar: gpg2: gpg: block_filter 0x00000000006edd10: read error (size=12276,a->size=12276)
>>> gpgtar: gpg2: gpg: block_filter 0x00000000006ee2e0: read error (size=13882,a->size=13882)
>>> gpgtar: gpg2: gpg: WARNING: encrypted message has been manipulated!
>>> gpgtar: gpg2: gpg: block_filter: pending bytes!
>>> gpgtar: gpg2: gpg: block_filter: pending bytes!
>>> gpgtar: error running '../../g10/gpg2': exit status 2
>>
>> We often see this error occur on Hydra as well. Retrying the build
>> eventually works, but it would be good to fix this.
>
> Isn’t it the same issue as
> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22558>? But that bug was
> closed.
It's true that the first message of bug 22558 mentioned two different
failure modes of gnupg-2.1.11's test suite. However, the subsequent
discussion focused on just one of those failure modes: the one that led
to 14 test failures. I closed the bug when that failure mode was
addressed.
In retrospect, since these two failure modes have different causes and
different fixes, perhaps I should have filed two separate bug reports
from the beginning. If we can agree on this, then perhaps we can
consider 22558 to address only the 14-test failure mode, and this bug
(22826) can address the gpgtar.test failure mode.
What do you think?
Mark
next prev parent reply other threads:[~2016-02-29 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 10:55 bug#22826: gnupg test failure Danny Milosavljevic
2016-02-27 13:18 ` Mark H Weaver
2016-02-28 15:51 ` Ludovic Courtès
2016-02-29 21:57 ` Mark H Weaver [this message]
2016-03-01 13:46 ` Ludovic Courtès
2018-02-05 22:14 ` Andreas Enge
2018-02-05 22:46 ` Leo Famulari
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=87bn6ztc0r.fsf@netris.org \
--to=mhw@netris.org \
--cc=22826@debbugs.gnu.org \
--cc=ludo@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 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).