-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] Library tests failing during linking for AOT - SIGKILL
#79569
Comments
Tagging subscribers to this area: @directhex Issue DetailsBuild Browser wasm Linux Release LibraryTests_AOT fails randomly on CI This might be caused by OOM as the wasm AOT builds are memory intensive. CI main run fail https://github.com/dotnet/runtime/runs/9978728829 PR fail https://github.com/dotnet/runtime/runs/10048986689
|
cc @radical |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBuild Browser wasm Linux Release LibraryTests_AOT fails randomly on CI This might be caused by OOM as the wasm AOT builds are memory intensive. CI main run fail - build, and log. PR fail https://github.com/dotnet/runtime/runs/10048986689
|
SIGKILL
during linking
SIGKILL
during linkingSIGKILL
A lot of instances of this are being seen, on windows, and linux. And not limited to For example, Microsoft.Extensions.Configuration.UserSecrets.Tests rolling build. The last few lines of
..
|
But the failures are not limited to helix, where the VMs have 4GB memory (IIUC). One rolling building failure was hit for System.Text.RegularExpressions.Tests which AOTs on the build machine itself (with 16GB memory, IIUC).
Did something regress recently to cause these? |
Could this be related to #79599? |
Can anyone reproduce this outside of CI ? |
Build Browser wasm Linux Release LibraryTests_AOT fails randomly on CI
This might be caused by OOM as the wasm AOT builds are memory intensive.
CI main run fail - build, and log.
PR fail https://github.com/dotnet/runtime/runs/10048986689
Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: