Repository navigation
Timeouts in crypto tests on Raspberry PIs #42379
Description
Activity
The update to OpenSSL 3 was around that time
commit 66da32c045035cf2710a48773dc6f55f00e20c40 Author: Daniel Bevenius <daniel.bevenius@gmail.com> Date: Wed Apr 14 11:19:54 2021 +0200 deps,test,src,doc,tools: update to OpenSSL 3.0 This pull request updates the OpenSSL version that is statically linked with Node.js from OpenSSl 1.1.1 to quictls OpenSSL 3.0.0+quic. This pull request will replace the OpenSSL version that is currently in the deps directory and when performing a normal build OpenSSL 3.0+quic will be statically linked to the Node.js executable. We will still be able to dynamically link to OpenSSL 1.1.1 and we have a CI job which dynamically links to OpenSSL 1.1.1 which is run for every pull request to make sure that we maintain backward compatibility. PR-URL: https://github.com/nodejs/node/pull/38512 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de>and it actually landed on the 11th.
My guess is that the update made things a bit slower which is why we are seeing the intermittent timeouts on the PIs
Reacted by Luigi Pinca- added a commit that references this issue
on Mar 17, 2022 My guess is that the update made things a bit slower
My guess is that a bug was introduced or at least an OS bug or limitation is now being exposed.
One thing that could help would be to modify the tests to either break them up into many smaller test files and/or to add some
console.log()statements so that when the test times out, we have some idea how far along it is and how long it was stuck in that state. Right now, all we know is that something locks up somewhere in these (often very long) test files but we have no idea where.- added a commit that references this issue
on Mar 18, 2022 - added a commit that references this issue
on Mar 21, 2022 - added 4 commits that reference this issue
on Apr 21, 2022 - added a commit that references this issue
on Apr 25, 2022 Since we no longer have Raspberry Pi's in our CI cluster, should we close this?
Reacted by Moshe Atlowagreed, closing.
Test
parallel/test-crypto-binary-default paralllel/test-crypto-dh-odd-key (3) parallel/test-crypto-binary-default (2) parallel/test-crypto-dh (2) parallel/test-crypto-dh-constructor (2) parallel/test-crypto-dh-leak (2)
Platform
ARM
Console output
Build links
Additional information
These have been flaky for quite a long time
I can see failures in
parallel/test-crypto-dhall the way back to October 14 2021 in the reliability reportl - nodejs/reliability#86