-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeouts in crypto tests on Raspberry PIs #42379
Comments
The update to OpenSSL 3 was around that time
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 |
Refs: nodejs#42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com>
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 |
Refs: #42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: nodejs#42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: #42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: nodejs#42379 A number of tests have been failing internmittently on the Rasberry PIs with timeouts since the update to OpenSSL 3.0. Give them more time. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#42380 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Since we no longer have Raspberry Pi's in our CI cluster, should we close this? |
agreed, 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-dh
all the way back to October 14 2021 in the reliability reportl - nodejs/reliability#86The text was updated successfully, but these errors were encountered: