Reenabled key exchange connection limiter test for macos. #1751
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1751 +/- ##
=======================================
Coverage 81.45% 81.46%
=======================================
Files 66 66
Lines 20508 20508
=======================================
+ Hits 16704 16706 +2
+ Misses 3804 3802 -2 ☔ View full report in Codecov by Sentry. |
davidv1992
force-pushed
the
reenable-key-exchange-connection-limiter-test
branch
from
6a3ea3c to
0c6a3a5
Compare
davidv1992
force-pushed
the
reenable-key-exchange-connection-limiter-test
branch
from
0c6a3a5 to
456455b
Compare
rnijveld
previously approved these changes
Dec 11, 2024
|
This was merged together with #1767 |
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.
Closes #1525
Fix of underlying cause was in #1739, together with a higher timeout to ensure the test also succeeds on efficiency cores.