bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#22826: gnupg test failure


From: Mark H Weaver
Subject: bug#22826: gnupg test failure
Date: Sat, 27 Feb 2016 08:18:30 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.91 (gnu/linux)

Danny Milosavljevic <address@hidden> 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) <address@hidden>"
> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created 
> 2003-12-31
> gpgtar: gpg2:       "Test two (no pp) <address@hidden>"
> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created 
> 2003-12-31
> gpgtar: gpg2:       "Test two (no pp) <address@hidden>"
> 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.

      Mark





reply via email to

[Prev in Thread] Current Thread [Next in Thread]