-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
runtime-coreclr superpmi-collect failed with System.Net.Sockets.SocketException (55): No buffer space available #78541
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/runtime-infrastructure Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng/internal/_build/results?buildId=2044300 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
"BuildRetry": false
} cc @dotnet/jit-contrib. ReportSummary
|
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng/internal/_build/results?buildId=2044300 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
"BuildRetry": false
} cc @dotnet/jit-contrib. Report
Summary
Known issue validationBuild: 🔎
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng/internal/_build/results?buildId=2044300 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
"BuildRetry": false
} cc @dotnet/jit-contrib. Report
Summary
Known issue validationBuild: 🔎
|
as far as I can tell this comes from msbuild, not from tests, right? |
There is no repro and in general this is not actionable. There are many articles on internet about his and it seems environmental e.g. disperse after reboot. It seems to be related to state of the machine e.g. large number of connection or lack of kernel resources. So this specific failures looks like infrastructure to me. We can investigate if there is way how to reproduce it. |
Build Information
Build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2044300
Build error leg or test failing: coreclr Pri1 Runtime Tests Run OSX arm64 checked
Pull request: #78297
Error Message
Fill the error message using known issues guidance.
cc @dotnet/jit-contrib.
Report
Summary
Known issue validation
Build: 🔎⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Result validation:
The text was updated successfully, but these errors were encountered: