-
Notifications
You must be signed in to change notification settings - Fork 698
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
V2 Integration isssue on Arm/nix #4568
Labels
Comments
Can we get the actual errors that occurred when these tests failed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Security issue notifications
If you discover a potential security issue in s2n we ask that you notify
AWS Security via our vulnerability reporting page. Please do not create a public github issue.
Problem:
As part of #3841, we're chasing down tests that fail under Nix on only Arm instances, needing extra retries. Specifically:
These flaky marks only apply to Arm, so no changes to the flaky settings should affect tests running on x86.
These values were arrived at by trial and error, running on CodeBuild (graviton2, 8 cores).
Steps taken to rule these out as an s2n issue
--durations=10
Same result. Slowest test was the failed test, at the timeout value of 60 seconds.
test_s2n_client_renegotiate_with_client_auth_with_openssl
test to a new test file, all by itself, still timing out on the same parameters.test_renegotiate_client.py::test_s2n_client_renegotiate_with_client_auth_with_openssl[OpenSSL-TLS1.2-RSA_2048_SHA512-P-384-ECDHE-RSA-AES128-GCM-SHA256]
ECDHE_RSA_AES128_SHA,
, test passes.While this process wasn't done for all of the flaky tests above, I did observe the same timeouts == reruns across all of them.
Solution:
?
The text was updated successfully, but these errors were encountered: