-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Tracking issue for "WORKLOAD TIMED OUT" #90309
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=368974 Error Message{
"ErrorMessage": "ERROR: WORKLOAD TIMED OUT - Killing user command..",
"BuildRetry": false
}
|
This is a variation of #82637 |
@akoeplinger something is wrong w/ our classification when there is a crash in a test suite. Check out https://dev.azure.com/dnceng-public/public/_build/results?buildId=494600&view=ms.vss-test-web.build-test-results-tab&runId=11481726&resultId=179767 for example. The net.dot log is huge (350MB) and seems to be logging a crash over and over again. |
The classification itself is correct, we're timing out because of the crash log loop. I see a potential reason for this, discussing it on Discord. |
Tagging subscribers to this area: @directhex, @matouskozak |
Closing this issue because the error message is too general and is matching all kinds of failures (see dotnet/xharness#1188). |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=368974
Build error leg or test failing:
Pull request: #90119
Error Message
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=368974
Error message validated:
ERROR: WORKLOAD TIMED OUT - Killing user command
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/10/2023 1:38:38 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: