The hosted runner encountered an error while running your job. (Error Type: Disconnect).

[lewing]

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=545844

Build leg reported

Build / osx-x64 Release AllSubsets_Mono_LLVMJIT

Pull Request

https://github.com/dotnet/runtime.git/pull/97694

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" : "The hosted runner encountered an error while running your job. (Error Type: Disconnect).",
    "BuildRetry": false,
    "ErrorPattern": "",
    "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

Report

Build	Definition	Step Name	Console log	Pull Request
810820	dotnet/runtime	osx-arm64 Debug AllSubsets_CoreCLR		dotnet/runtime#107923
810816	dotnet/runtime	tvos-arm64 Release AllSubsets_NativeAOT		dotnet/runtime#107810
807796	dotnet/sdk	AoT: macOS (x64)		dotnet/sdk#43393
796279	dotnet/sdk	Darwin Build_Release		dotnet/sdk#43085
2529254	dotnet-runtime	maccatalyst-arm64 release Mono
2528540	dotnet-runtime	Performance osx x64 release iOSMono JIT ios_scenarios perfiphone12mini NoJS False False True net9.0
2527001	dotnet-runtime	ios-arm64 release NativeAOT
787284	dotnet/runtime	maccatalyst-x64 Release AllSubsets_Mono		dotnet/runtime#80154

Summary

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

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=545844
Error message validated: The hosted runner encountered an error while running your job. (Error Type: Disconnect).
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/5/2024 8:24:46 PM UTC

[dougbu]

this looks a bunch like a low-level and transient issue in AzDO. they provide the macOS-12 images and, somehow, they're responsible for something (somewhere) deciding to deprovision the agent the job started on. have you seen this more than once❔

[lewing]

yes in dotnet/runtime#97766
https://dev.azure.com/dnceng-public/public/_build/results?buildId=547619&view=logs&jobId=7f49df26-8126-5de3-bf2f-6ac6bde01830

[garath]

Are you trying to use the "known error" feature here to find other occurances? There is no error message or pattern listed in the configuration blob of this issue, so it won't match to anything.

[dougbu]

not sure but we may not have any telemetry containing the interesting lines because they occur between build steps

##[error]The hosted runner encountered an error while running your job. (Error Type: Disconnect).
,##[warning]Received request to deprovision: The request was cancelled by the remote provider.

and, in place of a step's log

Nothing to show. Final logs are missing. This can happen when the job is cancelled or times out.

@garath, @AlitzelMendez, @missymessa, do we preserve any logs other than those for individual build steps (and Helix work items) for known issue matching❔

[garath]

do we preserve any logs other than those for individual build steps (and Helix work items) for known issue matching❔

No. If AzDO isn't showing the log, then it's likely the data never got captured into AzDO's database. Everything else is driven from that.

[lewing]

not sure but we may not have any telemetry containing the interesting lines because they occur between build steps

##[error]The hosted runner encountered an error while running your job. (Error Type: Disconnect).
,##[warning]Received request to deprovision: The request was cancelled by the remote provider.

and, in place of a step's log

Nothing to show. Final logs are missing. This can happen when the job is cancelled or times out.

@garath, @AlitzelMendez, @missymessa, do we preserve any logs other than those for individual build steps (and Helix work items) for known issue matching❔

I didn't expect it to work so I didn't add the message at first but it does appear to be able to match on that so I updated it and now some results are showing up.