From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#22826: gnupg test failure Date: Mon, 29 Feb 2016 16:57:56 -0500 Message-ID: <87bn6ztc0r.fsf@netris.org> References: <20160227115539.49203a2a@scratchpost.org> <87egbythp5.fsf@netris.org> <87r3fwx27n.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51624) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaVqL-0006Qy-Gg for bug-guix@gnu.org; Mon, 29 Feb 2016 16:59:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaVqI-0001d0-8v for bug-guix@gnu.org; Mon, 29 Feb 2016 16:59:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57086) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaVqI-0001cw-4x for bug-guix@gnu.org; Mon, 29 Feb 2016 16:59:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aaVqH-0001TF-R0 for bug-guix@gnu.org; Mon, 29 Feb 2016 16:59:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: 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") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 22826@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver skribis: > >> Danny Milosavljevic 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.d= rv' failed with exit code 1 >>> cannot build derivation `/gnu/store/ixcbdqm2xvclfnz4d25nv53wnp6x7alh-pr= ofile.drv': 1 dependencies couldn't be built >>> cannot build derivation `/gnu/store/904rahmy35wrhsfdb26pcfxyirhbmlnk-sy= stem.drv': 1 dependencies couldn't be built >>> note: keeping build directory `/tmp/guix-build-linux-libre-4.4.3-gnu.ta= r.xz.drv-0' >>> guix system: error: build failed: build of `/gnu/store/904rahmy35wrhsfd= b26pcfxyirhbmlnk-system.drv' failed >>> >>> More details: >>> >>> FAIL: gpgtar.test >>> Test: gpgtar.test >>> GNUPGHOME=3D/tmp/guix-build-gnupg-2.1.11.drv-0/gnupg-2.1.11/tests/openp= gp >>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, create= d 2003-12-31 >>> gpgtar: gpg2: "Test two (no pp) " >>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, create= d 2003-12-31 >>> gpgtar: gpg2: "Test two (no pp) " >>> gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, create= d 2003-12-31 >>> gpgtar: gpg2: "Test two (no pp) " >>> gpgtar: gpg2: gpg: block_filter 0x00000000006edd10: read error (size=3D= 12276,a->size=3D12276) >>> gpgtar: gpg2: gpg: block_filter 0x00000000006ee2e0: read error (size=3D= 13882,a->size=3D13882) >>> 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=E2=80=99t it the same issue as > ? 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