--- Begin Message ---
|
Subject: |
gnupg-2.1.11 on x86_64 failed its tests many times on Hydra |
|
Date: |
Thu, 04 Feb 2016 14:58:42 -0500 |
gnupg-2.1.11 on x86_64 failed its tests many times on Hydra:
http://hydra.gnu.org:3000/build/990803#tabs-buildsteps
On all other architectures (i686, armhf, mips64el) it succeeded on the
first try. So far, we've heard no reports of it failing for anyone else
on x86_64. Ludovic built it 3 times on his x86_64 machine and it never
failed.
It failed in at least two different ways:
* With only 1 test failure: gpgtar.test. This happened on at least two
different build slaves.
* With 14 test failures. This happened at least twice, on
hydra.gnunet.org.
I've attached 4 of the failure logs retrieved from Hydra. There are two
logs of each of the two failure modes described above.
It would be good to understand what happened here.
Mark
gnupg-2.1.11-x86_64-failure-logs.tar.xz
Description: hydra gnupg-x86_64 failure logs
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#22558: gnupg-2.1.11 on x86_64 failed its tests many times on Hydra |
|
Date: |
Fri, 12 Feb 2016 21:13:55 -0500 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.90 (gnu/linux) |
Leo Famulari <address@hidden> writes:
> On Fri, Feb 12, 2016 at 06:22:46PM -0500, Mark H Weaver wrote:
>> address@hidden (Ludovic Courtès) writes:
>>
>> > Eric Bavier <address@hidden> 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.
Mark
--- End Message ---