-
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
System.Runtime.Numerics.Tests.WorkItemExecution failure terminate the process because of out of memory #90439
Comments
Tagging subscribers to this area: @dotnet/area-system-numerics Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=371391 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.Runtime.Numerics.Tests",
"ErrorPattern": "Out of memory: Killed process",
"BuildRetry": false,
"ExcludeConsoleLog": false
} Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=371391
|
I spot checked a few of these and they seem to be in the outerloop runs. It would be nice if could distinguish the pipeline name in the report table. |
Added this to our 9.0.0 list because of the frequency |
Looks to be still a problem with |
removing blocking-clean-ci as it has not failed in 30 days
|
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=371391
Build error leg or test failing: System.Runtime.Numerics.Tests.WorkItemExecution
Pull request: #90417
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=371391
Error message validated:
Out of memory: Killed process
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/11/2023 11:28:54 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: