dotnet
[outerloop] System.Runtime.Numerics.Tests crash with exit code 137 in linux debug coreclr
Perhaps related to https://github.com/dotnet/runtime/issues/98964
Starting: System.Runtime.Numerics.Tests (parallel test collections = on, max threads = 2)
./RunTests.sh: line 168: 21 Killed "$RUNTIME_PATH/dotnet" exec --runtimeconfig System.Runtime.Numerics.Tests.runtimeconfig.json --depsfile System.Runtime.Numerics.Tests.deps.json xunit.console.dll System.Runtime.Numerics.Tests.dll -xml testResults.xml -nologo -nocolor -trait category=OuterLoop -notrait category=IgnoreForCI -notrait category=failing $RSP_FILE
/root/helix/work/workitem/e
----- end Mon Jul 8 23:40:00 UTC 2024 ----- exit code 137 ----------------------------------------------------------
exit code 137 means SIGKILL Killed eg by kill
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=733224 Build error leg or test failing: System.Runtime.Numerics.Tests.WorkItemExecution Pull request: https://github.com/dotnet/runtime/pull/104501
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "",
"ErrorPattern": "Killed.+System\\.Runtime\\.Numerics\\.Tests\\.runtimeconfig\\.json.+OuterLoop",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=733224
Error message validated: [Killed.+System\.Runtime\.Numerics\.Tests\.runtimeconfig\.json.+OuterLoop]
Result validation: :white_check_mark: Known issue matched with the provided build.
Validation performed at: 7/9/2024 4:39:02 AM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 4 | 28 | 107 |
Tagging subscribers to this area: @dotnet/area-system-numerics See info in area-owners.md if you want to be subscribed.
![dotnet-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/285228?v=4 "Published by a pub.dev verified publisher"){kind=small}
There is no dump and the only hint as to why the SIGKILL might have been raised is
dmesg: read kernel buffer failed: Operation not permitted
This seems like a more general flaky issue and not related to anything in the tests. I've not been able to repro locally so there's not much that can be done without some additional context or a reliable repro
This is the highest-hitting libraries known build issue. Worth a look if you can determine the cause. https://helix.dot.net/BuildAnalysis/KnownIssues @tannergooding @jeffhandley
