Remove TLS key gen from networking tests #2596
Merged
Conversation
This file contains 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
StephenButtolph
added
testing
patrick-ogrady
approved these changes
Jan 9, 2024
| if err != nil { | ||
| panic(err) | ||
| } | ||
| tlsCerts = []*tls.Certificate{ |
There was a problem hiding this comment.
Confirmed that we usually use 2-3 certs in our tests.
abi87
approved these changes
Jan 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why this should be merged
Currently RSA keygen can take so long that CI occasionally flakes. This removes the key generation for the first 3 certificates (which is all of the certs we currently use).
How this works
Hardcodes 3 test certificates.
How this was tested