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
2468915 dotnet-performance osx 13 x64 maui_scenarios_ios mono iPhoneMini12 8.0_Link
2468479 dotnet-performance osx 13 x64 maui_scenarios_ios mono iPhoneMini12 8.0_Link
697753 dotnet/runtime coreclr Pri0 Runtime Tests Run osx arm64 checked dotnet/runtime#102736
692513 dotnet/runtime Build OSX x64 release Runtime_Release dotnet/runtime#102558
2463271 dotnet-dotnet-monitor CodeQL MacOS arm64 Release
690106 dotnet/runtime osx-x64 Debug Mono_MiniJIT_LibrariesTests dotnet/runtime#102780
689470 dotnet/runtime osx-x64 Debug CoreCLR_Libraries dotnet/runtime#102754
689150 dotnet/runtime osx-x64 Debug Libraries_CheckedCoreCLR dotnet/runtime#102738
686590 dotnet/aspnetcore Test: macOS dotnet/aspnetcore#55865
686579 dotnet/runtime CoreCLR Product Build OSX x64 release dotnet/runtime#102558
686582 dotnet/runtime Build MacCatalyst x64 Release AllSubsets_Mono dotnet/runtime#102558
685385 dotnet/runtime Build MacCatalyst x64 Release AllSubsets_Mono dotnet/runtime#102558
680066 dotnet/sdk iOSSimulator_Shortstack_arm64 dotnet/sdk#40988
2454010 dotnet-runtime iossimulator-x64 release NativeAOT
2453853 dotnet-runtime Libraries SuperPMI collection libraries_tests Checked coreclr osx arm64 Release
2452705 dotnet-runtime iossimulator-arm64 release NativeAOT
2452680 dotnet-performance osx 13 x64 maui_scenarios_ios iPhoneMini12 release/7.0
677500 dotnet/sdk Darwin Build_Release dotnet/sdk#40887
673710 dotnet/aspnetcore Tests: macOS dotnet/aspnetcore#55691
673708 dotnet/aspnetcore Build: macOS x64 dotnet/aspnetcore#55691
2449760 dotnet-runtime Libraries SuperPMI collection libraries_tests_no_tiered_compilation Checked coreclr osx arm64 Release

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 3 21
@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