-
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
NonDisposedSocket_SafeHandlesCollected timed out after 900 seconds and was killed #50068
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsLogs at
|
We need stats about the frequency of this failure, so I raised #50104. |
This test should no longer timeout but fail instead. I recommend to close the issue and open a new one in case we notice failures. I expect the occurrences to be extremely rare. |
Occurred again:
|
According to Kusto data, this is a regular failure that doesn't depend on OS. Line 756 belongs to If connecting 100 socket pairs asynchronously can lead to hangs, that might be a sign a product bug. |
Logs at
https://dev.azure.com/dnceng/public/_build/results?buildId=1050964&view=logs&j=71afe768-e493-597c-228c-037834193aeb&t=fe87d331-02fa-5ca6-e382-69b0a11bb0f6&l=153
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-49786-merge-3cc1bbe3140144248c/System.Net.Sockets.Tests/console.b9794aa3.log?sv=2019-07-07&se=2021-04-11T19%3A25%3A54Z&sr=c&sp=rl&sig=c1Q2MBo%2Ft8wLihxAKfEk%2Ff6POoI%2BSq1o3hLVtl0pu0I%3D
The text was updated successfully, but these errors were encountered: