From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: NSS test failure on armhf
Date: Mon, 17 Apr 2017 17:52:34 -0400 [thread overview]
Message-ID: <20170417215234.GA32573@jasmine> (raw)
In-Reply-To: <874lxmlodc.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Mon, Apr 17, 2017 at 11:23:43PM +0200, Marius Bakke wrote:
> Hello!
>
> Since version 3.30.1, one test consistently fails on armhf. It is the
> same as in this bug report, although we don't see the exception:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1351459
>
> I initially thought this was due to stalls in the build process as we've
> seen before and tried increasing the timeouts in a790f2620, but that
> should probably be reverted.
>
> What should we do? We can either patch out this test, or go back to
> 3.30. Here are the release notes for 3.30.1:
>
> https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.30.1_release_notes
>
> It fixes a non-public bug in the base64 implementation, but introduced a
> test failure on at least two arches.
>
> Any preference?
Since there were no changes to the set of certificates between 3.30 and
3.30.1 [0], I would revert it for now.
[0]
https://wiki.mozilla.org/NSS:Release_Versions
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-17 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 21:23 NSS test failure on armhf Marius Bakke
2017-04-17 21:52 ` Leo Famulari [this message]
2017-04-17 22:35 ` Marius Bakke
2017-04-20 18:39 ` Mark H Weaver
2017-04-20 18:49 ` Leo Famulari
2017-04-20 19:28 ` Marius Bakke
2017-04-20 19:43 ` Marius Bakke
2017-04-20 21:14 ` Marius Bakke
2017-04-20 21:52 ` Mark H Weaver
2017-04-20 22:18 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170417215234.GA32573@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.