-
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
Tests failed: Wasm.Build.Tests.BlazorWasmBuildPublishTests due to SIGKILL #70985
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFailing tests: Wasm.Build.Tests.BlazorWasmBuildPublishTests due to SIGKILL Affected tests:
Failures as of 6/20:
Platform: net7.0-Browser-Release-wasm-Mono_Release_Linux-BuildWasmApps-Ubuntu.1804.Amd64.Open Output example:
|
Given the high impact on CI, we should consider disabling the tests. |
@radical Were these tests disabled? If so we can remove the |
I'm still hitting this: |
Yeah, these tests are different. It's the blazor AOT build is getting OOMkilled. We have lot of other tests building blazor projects with AOT too, but they work fine. And even these fails some times, so the memory usage likely skirts close to the edge most of the time. But I will try to see what we can do about it. |
Newly failing tests:
|
Failing tests: Wasm.Build.Tests.BlazorWasmBuildPublishTests due to SIGKILL
Affected tests:
Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTInProjectFile
Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTOnCommandLine
Wasm.Build.Tests.BlazorWasmBuildPublishTests.NativeBuild_WithDeployOnBuild_UsedByVS
Failures as of 6/20:
Platform: net7.0-Browser-Release-wasm-Mono_Release_Linux-BuildWasmApps-Ubuntu.1804.Amd64.Open
Output example:
Report
Summary
The text was updated successfully, but these errors were encountered: