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

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

Open
3 tasks
lewing opened this issue Jan 30, 2024 · 6 comments
Open
3 tasks

Comments

@lewing
Copy link
Member

lewing commented Jan 30, 2024

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
827742 dotnet/runtime Libraries Test Run checked coreclr osx x64 Debug dotnet/runtime#108555
826676 dotnet/sdk TestBuild: macOS (x64) dotnet/sdk#43887
823617 dotnet/sdk TestBuild: macOS (x64) dotnet/sdk#43239
822255 dotnet/runtime tvos-arm64 release MonoAOTOffsets dotnet/runtime#108391
820920 dotnet/runtime osx-x64 Debug AllSubsets_Mono_LLVMAOT dotnet/runtime#107772
820917 dotnet/runtime osx-x64 Release AllSubsets_Mono_Interpreter_RuntimeTests monointerpreter dotnet/runtime#108348
2548225 dotnet-runtime osx-arm64 release CrossAOT_Mono crossaot
820805 dotnet/runtime osx-x64 release Installer_Build_And_Test dotnet/runtime#103450
820876 dotnet/runtime osx-x64 Release Libraries_CheckedCoreCLR
820871 dotnet/runtime Mono ios AOT offsets
820749 dotnet/runtime osx-x64 release Installer_Build_And_Test dotnet/runtime#108153
820786 dotnet/runtime osx-arm64 Debug AllSubsets_CoreCLR dotnet/runtime#107943
820783 dotnet/runtime osx-arm64 Debug AllSubsets_CoreCLR dotnet/runtime#107943
820780 dotnet/sdk iOSSimulator_Shortstack_arm64 dotnet/sdk#43765
820756 dotnet/runtime osx-arm64 Release Libraries_CheckedCoreCLR
820720 dotnet/machinelearning MacOS_x64_Net60 Release_Build dotnet/machinelearning#7247
820703 dotnet/runtime osx-x64 Debug Libraries_CheckedCoreCLR dotnet/runtime#108340
820618 dotnet/runtime osx-x64 Debug Libraries_CheckedCoreCLR dotnet/runtime#108339
820520 dotnet/runtime Libraries Test Run checked coreclr osx x64 Release
820594 dotnet/runtime osx-x64 Debug Mono_MiniJIT_LibrariesTests dotnet/runtime#108337
2548079 dotnet-aspnetcore Build: macOS arm64
820467 dotnet/runtime tvos-arm64 Release AllSubsets_Mono dotnet/runtime#108334
820396 dotnet/runtime osx-arm64 debug Mono_Runtime dotnet/runtime#108156
820337 dotnet/sdk TemplateEngine: macOS (x64) dotnet/sdk#43753
820309 dotnet/runtime osx-arm64 Release NativeAOT_Libraries dotnet/runtime#108324
819897 dotnet/performance windows 22H2 x64 roslyn Open main dotnet/performance#4487
2545821 dotnet-runtime maccatalyst-arm64 release NativeAOT
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

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 4 30

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
Copy link
Member

dougbu commented Jan 30, 2024

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❔

@garath
Copy link
Member

garath commented Jan 31, 2024

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
Copy link
Member

dougbu commented Feb 1, 2024

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
Copy link
Member

garath commented Feb 1, 2024

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
Copy link
Member Author

lewing commented Feb 6, 2024

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.

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

3 participants