-
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
emcc received SIGKILL #79874
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Build InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=117528 Error MessageFill the error message using known issues guidance. {
"ErrorMessage": "dotnet.wasm --detect-features' failed (received SIGKILL (-9)",
"BuildRetry": false
}
|
@lewing @radical @kg @radekdoulik This has failed a lot in the past month. Can we disable the test until the error is understood? |
We are actively working on fixing this. I can look at disabling (the whole library tests run with aot), if it isn't fixed in a couple of days. |
Sorry about the delay, we crossed a previously unknown tipping point with some codegen changes and the underlying cause wasn't clear. We've identified the cause, a post link optimization pass that uses a ton of memory when updating dwarf debug information with relocations, and resolved the CI issues. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=117528
Build error leg or test failing: normal-System.Runtime.Tests.WorkItemExecution
Pull request: #79872
Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: