From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 35530@debbugs.gnu.org
Subject: bug#35530: NSS-3.43 fails its test suite on armhf-linux
Date: Fri, 03 May 2019 00:02:38 +0200 [thread overview]
Message-ID: <878svowm4h.fsf@elephly.net> (raw)
In-Reply-To: <878svpn6g6.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> NSS-3.43 fails its test suite on armhf-linux:
>
> https://hydra.gnu.org/build/3484222
I can reproduce this. Looks like all problems are with the tests in
ssl_drop_unittest.cc:
ssl_drop_unittest.cc:182: Failure
ssl_drop_unittest.cc:71: Failure
ssl_drop_unittest.cc:182: Failure
ssl_drop_unittest.cc:71: Failure
ssl_drop_unittest.cc:422: Failure
ssl_drop_unittest.cc:451: Failure
ssl_drop_unittest.cc:380: Failure
ssl_drop_unittest.cc:474: Failure
ssl_drop_unittest.cc:474: Failure
ssl_drop_unittest.cc:71: Failure
ssl_drop_unittest.cc:71: Failure
ssl_drop_unittest.cc:71: Failure
ssl_drop_unittest.cc:95: Failure
It’s a bit difficult to find actual test failures in the logs because it
mentions “error” and “failed” and the like a lot. This is a test that
counts ACKs after dropping parts of the messages / datagrams /
handshake. The failing tests seem to consistently come up short on ACKs
– they are not always zero but usually much lower than they are expected
to be.
--
Ricardo
next prev parent reply other threads:[~2019-05-02 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 22:41 bug#35530: NSS-3.43 fails its test suite on armhf-linux Mark H Weaver
2019-05-02 22:02 ` Ricardo Wurmus [this message]
2019-05-04 16:45 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878svowm4h.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35530@debbugs.gnu.org \
--cc=mhw@netris.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).