[Wasm][Test Failure] LoadLazyAssemblyBeforeItIsNeeded(lazyLoadingTestExtension: "wasm", allLazyLoadingTestExtensions: ["wasm", "dll", "NoExtension"])

[CarnaViire]

trafficstars

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=769868 Build error leg or test failing: Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.LoadLazyAssemblyBeforeItIsNeeded Pull request: https://github.com/dotnet/runtime/pull/105841

Error Message

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

{
  "ErrorMessage": "Could not find the pattern in the build output: '\\*\\* MicrosoftNetCoreAppRuntimePackDir : '([^ ']*)''.",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=769868 Error message validated: [Could not find the pattern in the build output: '\*\* MicrosoftNetCoreAppRuntimePackDir : '([^ ']*)''.] Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 8/8/2024 7:59:41 PM UTC

Report

Build	Definition	Test	Pull Request
843683	dotnet/runtime	Wasm.Build.Tests.TestAppScenarios.SatelliteLoadingTests.LoadSatelliteAssembly

Summary

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

[dotnet-policy-service[bot]]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries See info in area-owners.md if you want to be subscribed.

[lewing]

cc @maraf

[maraf]

Looking at offended builds, binlog always correctly contains PrintRuntimePackPath target and the message. Only the text output in log is missing it, including the standard dotnet build summary

Build succeeded. 0 Warning(s) 0 Error(s)

Time Elapsed 00:00:08.02

It checked for success exit code before. So, buffers in process wrapper?

[pavelsavara]

do we need to flush MSBuild stdout somehow ? Kill the process ?

[maraf]

There is a library for reading binlog https://www.nuget.org/packages/MSBuild.StructuredLogger. Maybe if we don't get "Build finished" message from the build process output, we can try to read all messages from binlog

[jkotas]

It checked for success exit code before. So, buffers in process wrapper?

We keep seeing reports of the redirected output being truncated mysteriously. For example, https://github.com/dotnet/runtime/issues/108395 filled a few days ago or https://github.com/dotnet/runtime/issues/100114#issuecomment-2099934576 from a few months ago. Given the variety of the reports, it points to a bug (race condition?) in System.Diagnostics.Process implementation.

[pavelsavara]

Is it possible that we are dealing with "msbuild server" process ?

[maraf]

Mitigated by reading the binlog

[pavelsavara]

@maraf could this be closed ?