Repository navigation
[Wasm][Test Failure] LoadLazyAssemblyBeforeItIsNeeded(lazyLoadingTestExtension: "wasm", allLazyLoadingTestExtensions: ["wasm", "dll", "NoExtension"]) #106160
Description
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: #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: 🔎 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: ✅ Known issue matched with the provided build.
Validation performed at: 8/8/2024 7:59:41 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Activity
dotnet-policy-service commentedon Aug 8, 2024
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.
lewing commentedon Aug 14, 2024
cc @maraf
maraf commentedon Sep 3, 2024
Looking at offended builds, binlog always correctly contains
PrintRuntimePackPathtarget and the message. Only the text output in log is missing it, including the standard dotnet build summaryIt checked for success exit code before. So, buffers in process wrapper?
pavelsavara commentedon Sep 24, 2024
do we need to flush MSBuild stdout somehow ? Kill the process ?
maraf commentedon Sep 27, 2024
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 commentedon Oct 4, 2024
We keep seeing reports of the redirected output being truncated mysteriously. For example, #108395 filled a few days ago or #100114 (comment) from a few months ago. Given the variety of the reports, it points to a bug (race condition?) in System.Diagnostics.Process implementation.
pavelsavara commentedon Oct 4, 2024
Is it possible that we are dealing with "msbuild server" process ?
maraf commentedon Oct 22, 2024
Mitigated by reading the binlog
pavelsavara commentedon Jul 18, 2025
@maraf could this be closed ?