[browser] Support CoreCLR in WebAssembly SDK #122495
.NET Result Analysis
Details
‼️ Build Analysis Check Result has been manually overridden
- The build analysis check result has been updated by the user for the following reason: known issues
https://github.com//issues/113686
https://github.com//issues/112360
https://github.com//issues/122669
https://github.com//issues/122671
- The check result has changed from Failure to Success
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Known test errors
Test Failures (4 tests failed)
🔹 [All failing tests from runtime]
- Exception Message
Return code: 1 Raw output file: C:hwB36209E0wAA97096Duploads egressions115178115178output.txt Raw output: BEGIN EXECUTION "C:hwB36209E0pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" 115178.dll Running RunTestUsingInfiniteWait test. Waiting for thread to enter wait... Starting thread waiting on event. Queue user APC. Waiting for APC to execute... Signaling wait event. Waiting for thread to leave wait... Stopping thread waiting on event. RunTestUsingInfiniteWait test executed. Running RunTestUsingTimedWait test. Waiting for thread to enter wait... Starting thread waiting on event. Queue user APC's. Stopping thread waiting on event. Waiting for thread to leave wait... RunTestUsingTimedWait test executed. Running RunTestInterruptInfiniteWait test. Waiting for thread to enter wait... Starting thread waiting on event. Queue user APC. Waiting for APC to execute... mono_thread_info_install_interrupt: previous_token should be INTERRUPT_STATE (FFFFFFFFFFFFFFFF), but it was 0000021CF36D43A0 Expected: 100 Actual: -1073740791 END EXECUTION - FAILED FAILED Test failed. Trying to see if dump file was created in C:cores since 12/19/2025 6:03:02 PM Processing C:corescorerun.exe.20476.dmp Invoking: C:Program Files (x86)Windows Kits10Debuggersdcdb.exe -c "$<C:hwB36209E0 mp2irycn.tmp" -z "C:corescorerun.exe.20476.dmp" stdout: Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:corescorerun.exe.20476.dmp]
User Mini Dump File with Full Memory: Only application data is available************* Path validation summary **************
Response Time (ms) Location
OK C:hwB36209E0pPDB
Symbol search path is: C:hwB36209E0pPDB
Executable search path is:
Windows 10 Version 14393 MP (4 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
10.0.14393.6343 (rs1_release.230913-1727)
Machine Name:
Debug session time: Fri Dec 19 18:03:06.000 2025 (UTC + 0:00)
System Uptime: 0 days 0:35:18.983
Process Uptime: 0 days 0:00:03.000
................................************* Symbol Loading Error Summary **************
Module name Error
ntdll The system cannot find the file specifiedYou can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(4ffc.1828): Security check failure or stack buffer overrun - code c0000409 (first/second chance not available)
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for coreclr.dll
coreclr!mono_gc_make_root_descr_all_refs+0x4c635:
00007ffc`35224ae5 cd29 int 29h
0:007> cdb: Reading initial command '$<C:hwB36209E0 mp2irycn.tmp'
0:007> .cordll -lp "C:hwB36209E0p"
CLRDLL: Consider using ".cordll -lp <path>" command to specify .NET runtime directory.
CLR DLL status: ERROR: Unable to load DLL C:hwB36209E0pmscordaccore_AMD64_AMD64_42.42.42.42424.dll, Win32 error 0n87
0:007> .load C:Users
unner.dotnetsossos.dll
0:007> ~*k0 Id: 4ffc.51f0 Suspend: 0 Teb: 00000078`0fb9b000 Unfrozen
Child-SP RetAddr Call Site
00000078`0fd7eae8 00007ffc`66eb0ce1 ntdll!ZwWaitForAlertByThreadId+0x14
00000078`0fd7eaf0 00007ffc`351a62dd ntdll!RtlAcquireSRWLockExclusive+0x121
00000078`0fd7eb50 00007ffc`351a6b6d coreclr!mono_gc_reference_queue_free+0xdd
00000078`0fd7eb90 00007ffc`351a7e5b coreclr!mono_object_hash+0xed
00000078`0fd7ebd0 00007ffc`3512530c coreclr!mono_monitor_enter_v4+0x27b
00000078`0fd7ec50 0000021c`f3661034 coreclr!mono_lookup_icall_symbol+0xb6ec
00000- CallStack
at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 142 at Xunit.Assert.True(Boolean condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 123 at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix) at Program.<<Main>$>g__TestExecutor3|0_4(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)
- Exception Message
Expected 0 exit code but got 1: C:\Program Files\nodejs\npm.cmd install Standard Output: [] npm error code ECONNRESET [] npm error network aborted [] npm error network This is a problem related to network connectivity. [] npm error network In most cases you are behind a proxy or have bad network settings. [] npm error network [] npm error network If you are behind a proxy, please make sure that the [] npm error network 'proxy' config is set properly. See: 'npm help config' [] npm notice [] npm notice New major version of npm available! 10.9.4 -> 11.7.0 [] npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.7.0 [] npm notice To update run: npm install -g npm@11.7.0 [] npm notice [] npm error A complete log of this run can be found in: C:\Users\ContainerAdministrator\AppData\Local\npm-cache\_logs\2025-12-19T19_25_43_173Z-debug-0.log
- CallStack
at Wasm.Build.Tests.CommandResult.EnsureExitCode(Int32 expectedExitCode, String messagePrefix, Boolean suppressOutput) in /_/src/mono/wasm/Wasm.Build.Tests/Common/CommandResult.cs:line 51 at Wasm.Build.Tests.CommandResult.EnsureSuccessful(String messagePrefix, Boolean suppressOutput) in /_/src/mono/wasm/Wasm.Build.Tests/Common/CommandResult.cs:line 28 at Wasm.Build.Tests.WasmTemplateTestsBase.BuildProjectCore(ProjectInfo info, Configuration configuration, MSBuildOptions buildOptions, Nullable`1 isNativeBuild, Nullable`1 wasmFingerprintDotnetJs) in /_/src/mono/wasm/Wasm.Build.Tests/Templates/WasmTemplateTestsBase.cs:line 246 at Wasm.Build.Tests.WasmTemplateTestsBase.PublishProject(ProjectInfo info, Configuration configuration, PublishOptions publishOptions, Nullable`1 isNativeBuild, Nullable`1 wasmFingerprintDotnetJs) in /_/src/mono/wasm/Wasm.Build.Tests/Templates/WasmTemplateTestsBase.cs:line 175 at Wasm.Build.Tests.FilesToIncludeInFileSystemTests.LoadFilesToVfs(Boolean publish) in /_/src/mono/wasm/Wasm.Build.Tests/FilesToIncludeInFileSystemTests.cs:line 40 --- End of stack trace from previous location ---
❌ baseservices\threading\regressions\115178\115178\115178.cmd [Console] [Details] [Artifacts] [0.18% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
❌ JavascriptBundler-ST-Wasm.Build.Tests.WorkItemExecution [Console] [Details] [Artifacts] [0.73% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
❌ System.Data.OleDb.Tests.WorkItemExecution [Console] [Details] [Artifacts] [0.36% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: Timeout. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
❌ Wasm.Build.Tests.FilesToIncludeInFileSystemTests.LoadFilesToVfs(publish: True) [Console] [Details] [Artifacts] [0.14% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
Was this helpful?