GNU bug report logs - #25974
[PATCH 0/2] gnu: nss: Skip failing test on armhf.

Previous Next

Full log

View this message in rfc822 format

From: Marius Bakke <mbakke <at> fastmail.com>
To: Leo Famulari <leo <at> famulari.name>
Cc: 25974 <at> debbugs.gnu.org
Subject: bug#25974: [PATCH 0/2] gnu: nss: Skip failing test on armhf.
Date: Mon, 06 Mar 2017 23:16:43 +0100

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> On Sun, Mar 05, 2017 at 03:47:35PM +0100, Marius Bakke wrote:
>> Patch 2/2 in this series conditionally skips the failing test on armhf.
>> Unfortunately patch 1/2 will rebuild nss on all platforms; I could not
>> figure out how to achieve the same without 'modify-phases'.
>
> That's a minor issue. Ping me when / if you push the change and I'll ask
> to evaluate the master branch.
>
>> Is this acceptable, or should we downgrade nspr and nss again?
>
> I do not think we should downgrade. I expect that most Guix users are
> using the new versions of NSS without any trouble on the x86_64
> architecture.
>
> We should either skip this test on armhf or downgrade the packages on
> armhf.
>
> Do we understand the nature of the test failure, and what sort of
> problems could be masked if we skip the test?

I see the build was restarted and this time it's a different error.

The test that failed in the first round was

"SkipVariants/TlsSkipTest.SkipCertAndKeyExch/0"

and in the second run it's

"ExtensionStream/TlsExtensionTestGeneric.NoSupportedGroups/2"

I also note that these two tests take on the order of 50ms under normal
conditions, but took 51499ms and 20492ms respectively when failing.

So it appears to be a problem with the build host rather than NSS
itself. Can you try starting it again? I guess the best solution is
increasing capacity of the build farm...

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.