Skip to content
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

Closed
karelz opened this issue Jun 20, 2022 · 6 comments · Fixed by #80241
Closed

Tests failed: Wasm.Build.Tests.BlazorWasmBuildPublishTests due to SIGKILL #70985

karelz opened this issue Jun 20, 2022 · 6 comments · Fixed by #80241
Assignees
Labels
arch-wasm WebAssembly architecture area-Build-mono disabled-test The test is disabled in source code against the issue
Milestone

Comments

@karelz
Copy link
Member

karelz commented Jun 20, 2022

Failing tests: Wasm.Build.Tests.BlazorWasmBuildPublishTests due to SIGKILL

Affected tests:

  • WithNativeReference_AOTInProjectFile -- Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTInProjectFile
  • WithNativeReference_AOTOnCommandLine -- Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTOnCommandLine
  • NativeBuild_WithDeployOnBuild_UsedByVS -- Wasm.Build.Tests.BlazorWasmBuildPublishTests.NativeBuild_WithDeployOnBuild_UsedByVS

Failures as of 6/20:

  • WithNativeReference_AOTInProjectFile
  • WithNativeReference_AOTOnCommandLine
  • NativeBuild_WithDeployOnBuild_UsedByVS

Platform: net7.0-Browser-Release-wasm-Mono_Release_Linux-BuildWasmApps-Ubuntu.1804.Amd64.Open

Output example:

Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTOnCommandLine:

[] emcc : error : '/datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NET.Runtime.Emscripten.3.1.7.Sdk.linux-x64/7.0.0-preview.6.22281.1/tools/bin/wasm-emscripten-finalize -g --dyncalls-i64 --dwarf /datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/obj/Debug/net7.0/wasm/for-publish/dotnet.wasm -o /datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/obj/Debug/net7.0/wasm/for-publish/dotnet.wasm --detect-features' failed (received SIGKILL (-9)) [/datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/blz_nativeref_aot_Debug.csproj]
[] /datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NET.Runtime.WebAssembly.Sdk/7.0.0-ci/Sdk/WasmApp.Native.targets(424,5): error MSB3073: The command "emcc "@/datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NETCore.App.Runtime.Mono.browser-wasm/7.0.0-ci/runtimes/browser-wasm/native/src/emcc-default.rsp" "@/datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NETCore.App.Runtime.Mono.browser-wasm/7.0.0-ci/runtimes/browser-wasm/native/src/emcc-link.rsp" "@/datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/obj/Debug/net7.0/wasm/for-publish/emcc-link.rsp"" exited with code 1. [/datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/blz_nativeref_aot_Debug.csproj]

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@karelz karelz added arch-wasm WebAssembly architecture blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' area-Build-mono blazor-wasm labels Jun 20, 2022
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jun 20, 2022
@ghost
Copy link

ghost commented Jun 20, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Failing tests: Wasm.Build.Tests.BlazorWasmBuildPublishTests due to SIGKILL

Affected tests:

  • WithNativeReference_AOTInProjectFile -- Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTInProjectFile
  • WithNativeReference_AOTOnCommandLine -- Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTOnCommandLine
  • NativeBuild_WithDeployOnBuild_UsedByVS -- Wasm.Build.Tests.BlazorWasmBuildPublishTests.NativeBuild_WithDeployOnBuild_UsedByVS

Failures as of 6/20:

  • WithNativeReference_AOTInProjectFile
  • WithNativeReference_AOTOnCommandLine
  • NativeBuild_WithDeployOnBuild_UsedByVS

Platform: net7.0-Browser-Release-wasm-Mono_Release_Linux-BuildWasmApps-Ubuntu.1804.Amd64.Open

Output example:

Wasm.Build.Tests.BlazorWasmBuildPublishTests.WithNativeReference_AOTOnCommandLine:

[] emcc : error : '/datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NET.Runtime.Emscripten.3.1.7.Sdk.linux-x64/7.0.0-preview.6.22281.1/tools/bin/wasm-emscripten-finalize -g --dyncalls-i64 --dwarf /datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/obj/Debug/net7.0/wasm/for-publish/dotnet.wasm -o /datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/obj/Debug/net7.0/wasm/for-publish/dotnet.wasm --detect-features' failed (received SIGKILL (-9)) [/datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/blz_nativeref_aot_Debug.csproj]
[] /datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NET.Runtime.WebAssembly.Sdk/7.0.0-ci/Sdk/WasmApp.Native.targets(424,5): error MSB3073: The command "emcc "@/datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NETCore.App.Runtime.Mono.browser-wasm/7.0.0-ci/runtimes/browser-wasm/native/src/emcc-default.rsp" "@/datadisks/disk1/work/B58909DD/w/A8850950/e/dotnet-workload/packs/Microsoft.NETCore.App.Runtime.Mono.browser-wasm/7.0.0-ci/runtimes/browser-wasm/native/src/emcc-link.rsp" "@/datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/obj/Debug/net7.0/wasm/for-publish/emcc-link.rsp"" exited with code 1. [/datadisks/disk1/work/B58909DD/w/A8850950/e/blz_nativeref_aot_Debug/blz_nativeref_aot_Debug.csproj]
Author: karelz
Assignees: -
Labels:

arch-wasm, blocking-clean-ci, area-Build-mono, blazor-wasm

Milestone: -

@karelz
Copy link
Member Author

karelz commented Jun 20, 2022

Given the high impact on CI, we should consider disabling the tests.

@radical radical self-assigned this Jun 20, 2022
@radical radical added disabled-test The test is disabled in source code against the issue and removed untriaged New issue has not been triaged by the area owner labels Jun 20, 2022
@agocke
Copy link
Member

agocke commented Jul 6, 2022

@radical Were these tests disabled? If so we can remove the blocking-clean-ci label

@radical radical removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Jul 6, 2022
@radical radical added this to the 7.0.0 milestone Jul 25, 2022
@radical radical modified the milestones: 7.0.0, 8.0.0 Aug 10, 2022
@stephentoub
Copy link
Member

stephentoub commented Dec 5, 2022

@radical
Copy link
Member

radical commented Dec 5, 2022

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.

@radical
Copy link
Member

radical commented Dec 5, 2022

Newly failing tests:

  • Wasm.Build.Tests.Blazor.MiscTests.NativeBuild_WithDeployOnBuild_UsedByVS
  • Wasm.Build.Tests.Blazor.MiscTests.DefaultTemplate_AOT_InProjectFile

@radical radical added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Dec 5, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jan 5, 2023
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jan 6, 2023
@radical radical removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Jan 6, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Feb 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Build-mono disabled-test The test is disabled in source code against the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants