-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
SslStreamNetworkStreamTest failing intermitently on OSX #46837
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsSee the logs here:
|
I don't see any failure in master branch but I do see one more recent failure in other PR. |
Failed in job runtime 20210114.72 Failed tests :
net6.0-OSX-Release-x64-Mono_release-OSX.1015.Amd64.Open Error messages:
|
@wfurt both |
ok. I'll try to reproduce it locally @hoyosjs |
@wfurt do you know if it is new test, or test/product regression introduced "recently"? |
It looks like it fails sometimes on server side with
it seems like OS does not like one (or more) certificates we passed in. Let me know if you have any hints how to debug this further @bartonjs @vcsjones. All the pointers look pointrish e.g. similar & high positive value. So far, I can reproduce it only when running in batch. |
I suspect this has been fixed since disabling the tests (e.g. by #57381). I put up PR which reenables the tests and they seem to pass. |
The underlying issue has been likely fixed by other changes
See the logs here:
https://dev.azure.com/dnceng/public/_build/results?buildId=945417&view=logs&j=c6f8dc49-92a1-5760-c098-ba97b8142bfb&t=22b0078b-0469-5ba6-8725-2121fdbae049&l=73
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-46786-merge-dccc925d8d224a72ae/System.Net.Security.Tests/console.8a016bf1.log?sv=2019-07-07&se=2021-01-31T21%3A35%3A41Z&sr=c&sp=rl&sig=s450sAj02mJX6juyepBSL48rnUMYeIe%2BD8VFbS5YgfM%3D
Runfo Tracking Issue: SslStreamNetworkStreamTest_Throws failing on OSX
Build Result Summary
The text was updated successfully, but these errors were encountered: