-
Notifications
You must be signed in to change notification settings - Fork 717
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
s2n: upgrade 1.3.50 -> 1.3.51 some unittests fail #4204
Comments
Thanks for the issue, can you provide the cmake banner and/or the platform, compiler, libcrypto used so we can try to reproduce this? |
This can be easy reproduced with yocto + meta-aws. As you see it's the same issue on all of those failed tests |
Hi @thomas-roos unfortunately we dont test/support the yocto platform so its non-trivial for us to repro this issue. However its curious why the build started failing since our CI didnt catch the regression. I am wondering If you might be able to help test and provide the commit which broke your build. I am also curious if there is a Github CI action (PRs welcome :D) which we can add to catch this regression at development time? Without this there is no guarantee to prevent breakage in the future also. Here is are the commits which were added between the two releases. |
Hi, |
Problem:
after upgrade some unit tests fail:
{'s2n': ['s2n_unittest:./s2n_blob_test',
's2n_unittest:./s2n_client_key_share_extension_pq_test',
's2n_unittest:./s2n_client_session_ticket_extension_test',
's2n_unittest:./s2n_early_data_test',
's2n_unittest:./s2n_ecc_evp_test',
's2n_unittest:./s2n_extensions_server_key_share_select_test',
's2n_unittest:./s2n_kem_test',
's2n_unittest:./s2n_pq_kem_test',
's2n_unittest:./s2n_psk_offered_test',
's2n_unittest:./s2n_psk_test',
's2n_unittest:./s2n_quic_support_io_test',
's2n_unittest:./s2n_quic_support_test',
's2n_unittest:./s2n_resume_test',
's2n_unittest:./s2n_stuffer_test',
's2n_unittest:./s2n_tls13_handshake_early_data_test',
's2n_unittest:./s2n_tls13_hybrid_shared_secret_test',
's2n_unittest:_./s2n_tls13_server_cert_test']}
unit_test_log.txt
The text was updated successfully, but these errors were encountered: