Re-enable SslStreamTlsResumeTests.ClientDisableTlsResume_Succeeds#124463
Re-enable SslStreamTlsResumeTests.ClientDisableTlsResume_Succeeds#124463
Conversation
Co-authored-by: rzikm <32671551+rzikm@users.noreply.github.com>
|
I can't reproduce the issue locally, I will see if it reproduces overnight, otherwise, I think we can merge this |
|
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones |
There was a problem hiding this comment.
Pull request overview
Re-enables the SslStreamTlsResumeTests.ClientDisableTlsResume_Succeeds functional test in System.Net.Security by removing the Windows-specific [ActiveIssue] skip, based on indications that the underlying SChannel/session resumption flakiness has been addressed.
Changes:
- Remove the
[ActiveIssue("https://github.com/dotnet/runtime/issues/103449", TestPlatforms.Windows)]attribute fromClientDisableTlsResume_Succeeds.
wfurt
left a comment
There was a problem hiding this comment.
I think we can try it. It may be timing problem and/or it may behave different way on different windows versions.
|
/ba-g test failures are not related |
|
The issue did not reproduce locally when run in a loop overnight (it used to in the past), so we can merge this. |
Description
Test
ClientDisableTlsResume_Succeedswas disabled on Windows due to flaky TLS session resumption behavior. Issue comments indicate the underlying SChannel bug was fixed in PR #113604, but the test remained disabled. Re-enabling to verify resolution in CI.Changes
[ActiveIssue]attribute fromClientDisableTlsResume_Succeedstest methodTest validates that setting
AllowTlsResume = falseproperly prevents TLS session resumption. Previously failed intermittently on Windows with sessions resuming when they shouldn't.Test Results
Both parameterized test cases pass on Linux:
ClientDisableTlsResume_Succeeds(testClient: True)ClientDisableTlsResume_Succeeds(testClient: False)CI will validate Windows behavior.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.