-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Safe handle use after close in System.Net.Security.Tests #46770
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRunfo Tracking Issue: Tracking issue in roslyn-ci
Build Result Summary
|
cc: @aik-jahoda |
Is this the same thing as #30724??? If, we should merge the issues into one. |
Triage: punting as #30724 |
@wfurt can you please add few details why it was reopened? I assume you reverted the changes ... |
yes, #58594 was reverted |
Do we know home much this is still happening @rzikm ? From the label it does not seem we disabled the tests. |
@wfurt, I don't see any recent hits in the CI results DB. Do we close the issue then? |
It somewhat worries me that it is magical fixed but I see no benefit of keeping it open. |
Agreed. Closing per above - no recent hits. |
One more thought on this: we generally eliminated all the tests that could dispose SslStream during use. I'm wondering if that is what triggers this pattern. And it would explain why we don't see field reports. |
Failures 5/27-7/27 (incl. PRs):
Latest
ClientAndServer_OneOrBothUseDefault_OkClientAndServer_OneOrBothUseDefault_Ok
tracking in #30724 (comment)Typical failure:
Details from runfo - seems to be invalid link
Build Result Summary
The text was updated successfully, but these errors were encountered: