[8.0][wasm] Exit code 137 returned from docker process after executing containerHandlerInvoker.js, cs files specified multiple times

[carlossanlop]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=593479
Build error leg or test failing: browser-wasm linux Release AllSubsets_Mono_RuntimeTests monointerpreter - Build Tests

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "##[error]Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000  -w /home/cloudtest_azpcontainer",
  "BuildRetry": true,
  "ExcludeConsoleLog": false
}

• Found in PR: [release/8.0][browser] Fix failures in CalendarTestBase affecting several globalization tests  #99407
• Queue: browser-wasm linux Release AllSubsets_Mono_RuntimeTests monointerpreter
• Job result: https://dev.azure.com/dnceng-public/public/_build/results?buildId=593479&view=logs&j=3e93a48f-6568-53f2-76b3-1285c183c39d&t=313dc435-bc2e-554b-c5b1-106790cdfaec&s=6884a131-87da-5381-61f3-d7acc3b91d76
• Failing step: Build tests
• Output:

First, a bunch of warning messages like this:

##[warning]CSC(0,0): warning CS2002: Source file '/__w/1/s/artifacts/tests/coreclr/obj/browser.wasm.Release/Managed/JIT/HardwareIntrinsics/General/Vector128_1/Vector128_1_r/Vector128_1_r/gen/op_LeftShift.Byte.cs' specified multiple times [/__w/1/s/src/tests/JIT/HardwareIntrinsics/General/Vector128_1/Vector128_1_r.csproj]

And then a final error message:

##[error]Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000  -w /home/cloudtest_azpcontainer 476633c25f864844c61bcb34e02519932b7de634f433aa15a2aeeaf5e3a8752a /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=593479
Error message validated: [##[error]Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000 -w /home/cloudtest_azpcontainer]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/7/2024 7:05:43 PM UTC

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[ilonatommy]

Between net9 and net8 there was a change in how we build for NativeAOT_* lanes, introduced in #101270. The code 137 is OOM and skipping building host looks like a probable fix for it. I am backporting the mentioned PR.

Edit: if it won't work, another PR that was optimizing this lane is: #98939.

[ilonatommy]

The initial analysis was incorrect, the issue is not purely NativeAOT-related.

• nativeaot hits will most likely be fixed by the GCServer disabling PR ([release/8.0-staging] Use workstation GC in outerloop NativeAOT libs runs #105794)
• monointerpreter on linux_86_64 log build command:
  /src/tests/build.sh ci os browser wasm Release -mono /p:RuntimeVariant=monointerpreter /p:LibrariesConfiguration=Release
  we have only one log available from this lane. We have this older issue: [wasm] Runtime tests' build gets terminated with exited with code 137 #94077 that also failed on building the managed dlls, on the line:
  

  runtime/src/tests/build.proj

  Line 611 in 03b4c79

  <GroupBuildCmd>$(GroupBuildCmd) /bl:$(ArtifactsDir)/log/$(Configuration)/InnerManagedTestBuild.$(__TestGroupToBuild).binlog</GroupBuildCmd>

  
  It was running with restricted parallelism (/m:1) while the log caught by this PR was running with /maxcpucount.

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.