Draft
Conversation
JeremiahM37
force-pushed
the
pythonCrypto
branch
3 times, most recently
from
802fec6 to
c8e8d25
Compare
JeremiahM37
force-pushed
the
pythonCrypto
branch
from
b16b334 to
ab807e8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is quite a bit failing with this still (12 tests). The biggest causes of failures are RSA tests. I created a patch for version 38.0.4 that removes l hard loading to openssl default and legacy provider. The only remaining crypto test failures are related to RSA, ECDSA, and AESGCM. To see a list of just the failing tests, add --lf -v --tb=no | grep "FAILED|ERROR" | awk '{print $1}' | sort | uniq | tee failed_tests.txt to the end of the python3 -m pytest command.