What did you do? ================ 1. Build NSS 3.29.2. 2. Run "./nss/tests/all.sh". What happened? ============== [ RUN ] SkipVariants/TlsSkipTest.SkipCertAndKeyExch/0 Version: TLS 1.1 server: Changing state from INIT to CONNECTING client: Changing state from INIT to CONNECTING Dropping handshake: 11 record old:  0200005703023cf5603f1d5df18055d2902e9279a1528cbe2f1484aad1a60762... record new:  0200005703023cf5603f1d5df18055d2902e9279a1528cbe2f1484aad1a60762... Dropping handshake: 12 record old:  0200005703023cf5603f1d5df18055d2902e9279a1528cbe2f1484aad1a60762... record new:  0200005703023cf5603f1d5df18055d2902e9279a1528cbe2f1484aad1a60762... server: Original packet:  16030202c30200005703023cf5603f1d5df18055d2902e9279a1528cbe2f1484... server: Filtered packet:  160302005f0200005703023cf5603f1d5df18055d2902e9279a1528cbe2f1484... Alert:  020a client: Handshake failed with error SSL_ERROR_RX_UNEXPECTED_HELLO_DONE: SSL received an unexpected Server Hello Done handshake message. client: Changing state from CONNECTING to ERROR tls_connect.cc:248: Failure Value of: (client_->state() != TlsAgent::STATE_CONNECTING) && (server_->state() != TlsAgent::STATE_CONNECTING) Actual: false Expected: true tls_connect.cc:374: Failure Value of: server_->state() Actual: CONNECTING Expected: TlsAgent::STATE_ERROR Which is: ERROR [ FAILED ] SkipVariants/TlsSkipTest.SkipCertAndKeyExch/0, where GetParam() = ("TLS", 770) (51499 ms) What should have happened? ========================== No errors. Is there anything else we should know? ======================================
Assignee: nobody → nobody
Component: Security → Test
Product: Mozilla Developer Network → NSS
Version: unspecified → 3.29
Can you reproduce this? There was an intermittent error at some point in the tests. I just ran the tests on armhf successfully.
I'm sorry for this false report. We've seen this intermittently on a busy armhf build slave, but it went away after simply increasing the timeouts.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.