Skip to content
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

Closed
JulieLeeMSFT opened this issue Nov 18, 2022 · 7 comments
Labels
area-System.Net.Sockets blocking-clean-ci-optional Blocking optional rolling runs Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@JulieLeeMSFT
Copy link
Member

JulieLeeMSFT commented Nov 18, 2022

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.

{
  "ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
  "BuildRetry": false
}

cc @dotnet/jit-contrib.

Report

Build Definition Step Name Console log Pull Request
2227823 dotnet-runtime Send tests to Helix (Unix) Log
2226350 dotnet-runtime Send tests to Helix (Unix) Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 2

Known issue validation

Build: 🔎
Result validation: ⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.

@JulieLeeMSFT JulieLeeMSFT added blocking-clean-ci-optional Blocking optional rolling runs Known Build Error Use this to report build issues in the .NET Helix tab labels Nov 18, 2022
@JulieLeeMSFT JulieLeeMSFT added this to the 8.0.0 milestone Nov 18, 2022
@dotnet-issue-labeler
Copy link

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.

@JulieLeeMSFT
Copy link
Member Author

Link

2022-11-14T06:22:14.5104150Z MSBUILD : error MSB4166: Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.
2022-11-14T06:22:14.5109060Z MSBUILD : error MSB4166: /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/MSBuild_pid-62011_23413a2766fc484ab1bee3f5452c9618.failure.txt:
2022-11-14T06:22:14.5111490Z MSBUILD : error MSB4166: UNHANDLED EXCEPTIONS FROM PROCESS 62011:
2022-11-14T06:22:14.5114230Z MSBUILD : error MSB4166: =====================
2022-11-14T06:22:14.5117660Z MSBUILD : error MSB4166: 11/14/2022 6:22:14 AM
2022-11-14T06:22:14.5118430Z MSBUILD : error MSB4166: System.IO.IOException: No buffer space available
2022-11-14T06:22:14.5119820Z MSBUILD : error MSB4166:  ---> System.Net.Sockets.SocketException (55): No buffer space available
2022-11-14T06:22:14.5121250Z MSBUILD : error MSB4166:    at System.IO.Pipes.PipeStream.WriteCore(ReadOnlySpan`1 buffer)
2022-11-14T06:22:14.5122960Z MSBUILD : error MSB4166:    --- End of inner exception stack trace ---
2022-11-14T06:22:14.5123760Z MSBUILD : error MSB4166:    at System.IO.Pipes.PipeStream.WriteCore(ReadOnlySpan`1 buffer)
2022-11-14T06:22:14.5125500Z MSBUILD : error MSB4166:    at Microsoft.Build.BackEnd.NodeEndpointOutOfProcBase.RunReadLoop(Stream localReadPipe, Stream localWritePipe, ConcurrentQueue`1 localPacketQueue, AutoResetEvent localPacketAvailable, AutoResetEvent localTerminatePacketPump)
2022-11-14T06:22:14.5126660Z MSBUILD : error MSB4166: ===================
2022-11-14T06:22:14.5127100Z MSBUILD : error MSB4166: 
2022-11-14T06:22:14.5127600Z MSBUILD : error MSB4166: 
2022-11-14T06:22:14.5133800Z ##[error]Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.

@ghost
Copy link

ghost commented Nov 18, 2022

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

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.

{
  "ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
  "BuildRetry": false
}

cc @dotnet/jit-contrib.

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
Author: JulieLeeMSFT
Assignees: -
Labels:

area-Infrastructure, blocking-clean-ci-optional, Known Build Error

Milestone: 8.0.0

@ghost
Copy link

ghost commented Jul 10, 2023

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

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.

{
  "ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
  "BuildRetry": false
}

cc @dotnet/jit-contrib.

Report

Build Definition Step Name Console log Pull Request
2210257 dotnet-runtime Send tests to Helix (Unix) Log
2209637 dotnet-runtime Send tests to Helix (Unix) Log
2203123 dotnet-runtime Send tests to Helix (Unix) Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 3

Known issue validation

Build: 🔎
Result validation: ⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.

Author: JulieLeeMSFT
Assignees: -
Labels:

area-System.IO, blocking-clean-ci-optional, Known Build Error

Milestone: 8.0.0

@ghost
Copy link

ghost commented Jul 17, 2023

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

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.

{
  "ErrorMessage": "System.Net.Sockets.SocketException (55): No buffer space available",
  "BuildRetry": false
}

cc @dotnet/jit-contrib.

Report

Build Definition Step Name Console log Pull Request
2210257 dotnet-runtime Send tests to Helix (Unix) Log
2209637 dotnet-runtime Send tests to Helix (Unix) Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 2

Known issue validation

Build: 🔎
Result validation: ⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.

Author: JulieLeeMSFT
Assignees: -
Labels:

area-System.Net.Sockets, blocking-clean-ci-optional, Known Build Error

Milestone: 8.0.0

@wfurt
Copy link
Member

wfurt commented Jul 17, 2023

as far as I can tell this comes from msbuild, not from tests, right?

@wfurt
Copy link
Member

wfurt commented Aug 10, 2023

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.

@wfurt wfurt closed this as completed Aug 10, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Sep 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets blocking-clean-ci-optional Blocking optional rolling runs Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

No branches or pull requests

5 participants