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

"We stopped hearing from agent Azure Pipelines 32. Verify the agent machine is running and has a healthy network connection" #1886

Open
3 tasks
jeffschwMSFT opened this issue Jan 24, 2024 · 2 comments

Comments

@jeffschwMSFT
Copy link
Member

jeffschwMSFT commented Jan 24, 2024

Build

https://dev.azure.com/dnceng/internal/_build/results?buildId=2361240

Error:

##[error]We stopped hearing from agent Azure Pipelines 32. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610

Build leg reported

No response

Pull Request

No response

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "",
    "BuildRetry": false,
    "ErrorPattern": "We stopped hearing from agent Azure Pipelines .*. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error.",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng/internal/_build/results?buildId=2361240
Error message validated: [We stopped hearing from agent Azure Pipelines .*. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/7/2024 1:03:13 AM UTC

Report

Build Definition Step Name Console log Pull Request
988422 dotnet/runtime osx-x64 Release AllSubsets_Mono_Minijit_RuntimeTests minijit dotnet/runtime#113592
2668296 dotnet-dotnet OSX_x64
2668246 dotnet-dotnet OSX_arm64
985966 dotnet/runtime coreclr Pri0 Runtime Tests Run osx arm64 checked dotnet/runtime#113576
980873 dotnet/runtime tvossimulator-x64 Release AllSubsets_NativeAOT_RuntimeTests
2662650 dotnet-sdk TestBuild: macOS (x64) #48424
973117 dotnet/runtime maccatalyst-x64 Release AllSubsets_Mono dotnet/runtime#112514
972353 dotnet/runtime osx-arm64 Release NativeAOT_Libraries dotnet/runtime#111666
970567 dotnet/runtime coreclr Pri0 Runtime Tests Run osx x64 checked dotnet/runtime#113206

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 4 9
@lewing
Copy link
Member

lewing commented Feb 8, 2024

#1919 is a similar looking mac host infra failure

@lewing
Copy link
Member

lewing commented Feb 8, 2024

as is #1883

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants