[browser] Wasm.Build.Tests timeout - Timed out after 10s waiting for 'WASM EXIT'

[jozkee]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1068222
Build error leg or test failing: NoWebcil-ST-Wasm.Build.Tests.MainWithArgsTests.WorkItemExecution
Pull request: #116639

Error Message

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

{
  "ErrorMessage": "Timed out after 10s waiting for 'WASM EXIT' messag",
  "ErrorPattern": "",
  "BuildRetry": true,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1068222
Error message validated: [Timed out after 10s waiting for 'WASM EXIT' messag]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 6/16/2025 4:06:50 PM UTC

Report

Build	Definition	Test	Pull Request
1161089	dotnet/runtime	Wasm.Build.Tests.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop	#120230
1156016	dotnet/runtime	Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithDisableRuntimeMarshallingAttribute_ConsideredBlittable(config: Release, aot: False)	#119992
1155832	dotnet/runtime	Wasm.Build.Tests.DiagnosticsTests.RunSimpleAppWithLogProfiler	#119683
1153831	dotnet/runtime	Wasm.Build.Tests.ModuleConfigTests.OutErrOverrideWorks
1145779	dotnet/runtime	Wasm.Build.Tests.NativeBuildTests.ZipArchiveInteropTest
1144990	dotnet/runtime	Wasm.Build.Tests.LazyLoadingTests.FailOnMissingLazyAssembly	#119561
1142805	dotnet/runtime	Wasm.Build.Tests.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop	#119476
1139643	dotnet/runtime	Wasm.Build.Tests.HttpTests.HttpNoStreamingTest	#119360
1139145	dotnet/runtime	Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithDisableRuntimeMarshallingAttribute_ConsideredBlittable(config: Release, aot: False)	#118810
1136713	dotnet/runtime	Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithDisableRuntimeMarshallingAttribute_ConsideredBlittable(config: Release, aot: False)	#118810

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
1	2	10

Report

Build	Definition	Test	Pull Request
1170612	dotnet/runtime	Wasm.Build.Tests.DllImportTests.DllImportWithFunctionPointersCompilesWithoutWarning(config: Release, aot: False)
1169444	dotnet/runtime	Wasm.Build.Tests.WasmRunOutOfAppBundleTests.RunOutOfAppBundle(config: Release, aot: False)
1162387	dotnet/runtime	Wasm.Build.Tests.BuildPublishTests.BuildThenPublishWithAOT(config: Release, aot: True)
1161590	dotnet/runtime	Wasm.Build.Tests.ModuleConfigTests.OutErrOverrideWorks	#119427
1161562	dotnet/runtime	Wasm.Build.Tests.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop	#120249
1161089	dotnet/runtime	Wasm.Build.Tests.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop	#120230
1156016	dotnet/runtime	Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithDisableRuntimeMarshallingAttribute_ConsideredBlittable(config: Release, aot: False)	#119992
1155832	dotnet/runtime	Wasm.Build.Tests.DiagnosticsTests.RunSimpleAppWithLogProfiler	#119683
1153831	dotnet/runtime	Wasm.Build.Tests.ModuleConfigTests.OutErrOverrideWorks

Summary

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

Report

Build	Definition	Test	Pull Request
1174160	dotnet/runtime	NoWebcil-ST-Wasm.Build.Tests.IcuShardingTests2.WorkItemExecution	#120519
1173927	dotnet/runtime	Wasm.Build.Tests.SatelliteLoadingTests.LoadSatelliteAssemblyFromReference	#120694
1173002	dotnet/runtime	NoWebcil-ST-Wasm.Build.Tests.WasmBuildAppTest.WorkItemExecution	#120477
1172421	dotnet/runtime	NoWebcil-ST-Wasm.Build.Tests.PInvokeTableGeneratorTests.WorkItemExecution	#120097
1170612	dotnet/runtime	Wasm.Build.Tests.DllImportTests.DllImportWithFunctionPointersCompilesWithoutWarning(config: Release, aot: False)
1169444	dotnet/runtime	Wasm.Build.Tests.WasmRunOutOfAppBundleTests.RunOutOfAppBundle(config: Release, aot: False)
1162387	dotnet/runtime	Wasm.Build.Tests.BuildPublishTests.BuildThenPublishWithAOT(config: Release, aot: True)
1161590	dotnet/runtime	Wasm.Build.Tests.ModuleConfigTests.OutErrOverrideWorks	#119427
1161562	dotnet/runtime	Wasm.Build.Tests.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop	#120249
1161089	dotnet/runtime	Wasm.Build.Tests.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop	#120230
1156016	dotnet/runtime	Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithDisableRuntimeMarshallingAttribute_ConsideredBlittable(config: Release, aot: False)	#119992
1155832	dotnet/runtime	Wasm.Build.Tests.DiagnosticsTests.RunSimpleAppWithLogProfiler	#119683
1153831	dotnet/runtime	Wasm.Build.Tests.ModuleConfigTests.OutErrOverrideWorks

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
2	6	13

[jozkee]

@dotnet/dnceng BA is not matching the error, presumably because is not in the console log? It's in xharness-output\testResults.xml.

[jozkee]

Duplicate of #113836 but for a different test.

[missymessa]

@dotnet/dnceng BA is not matching the error, presumably because is not in the console log? It's in xharness-output\testResults.xml.

@jozkee this documentations says where Known Issues can look at error information: https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssues.md#how-the-matching-process-works-between-a-known-issue-and-a-buildtest-error

[jozkee]

@missymessa looks to me xharness-output\testResults.xml is a helix log. I also set "ExcludeConsoleLog": true, assuming that gives more range in case the 100 logs limit was being reached.

But looks like BA gave up on this issue.

[missymessa]

@jozkee I can open an issue to investigate this. Are you currently blocked on this?

[jozkee]

No, I'm not blocked on it, thanks.

[lewing]

@jozkee this is too broad of a pattern to be useful. It will catch any timeout even newly introduced ones.

[jozkee]

@lewing I just broadened it because I saw LoadLazyAssemblyBeforeItIsNeeded (#113836) existed and I got #113836 (comment) I suspected more tests would fail and wouldn't be great to have one issue per each failing test. Feel free to adjust it.

[lewing]

KnownBuildErrors that can easily hide new regressions are actively harmful by making what should be failing CI look green. It is always a balance but blanket matches against a timeout are generally too broad.