l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <m...@netris.org> skribis:
>
>> Danny Milosavljevic <dan...@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) <t...@example.com>"
>>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created
>>> 2003-12-31
>>> gpgtar: gpg2: "Test two (no pp) <t...@example.com>"
>>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created
>>> 2003-12-31
>>> gpgtar: gpg2: "Test two (no pp) <t...@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
