.packages/microsoft.dotnet.helix.sdk/11.0.0-beta.25613.101/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.Composition.Tests in job 60697174-3724-4568-a287-50cfc5f148ad has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/60697174-3724-4568-a287-50cfc5f148ad/workitems/System.Composition.Tests/console

.packages\microsoft.dotnet.helix.sdk\11.0.0-beta.25613.101\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test baseservices\threading\regressions\115178\115178\115178.cmd has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/a4507db3-9fbe-4219-9e5f-ab7f78c40c3f/workitems/threading_group1/console

.packages\microsoft.dotnet.helix.sdk\11.0.0-beta.25613.101\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.Data.OleDb.Tests in job 2070e284-7e61-4bca-b075-72e7e153dcc6 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/2070e284-7e61-4bca-b075-72e7e153dcc6/workitems/System.Data.OleDb.Tests/console

.packages\microsoft.dotnet.helix.sdk\11.0.0-beta.25613.101\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item JavascriptBundler-ST-Wasm.Build.Tests in job e8f5ce00-d3fc-4dca-9921-310a0c487730 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/e8f5ce00-d3fc-4dca-9921-310a0c487730/workitems/JavascriptBundler-ST-Wasm.Build.Tests/console

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 specified

You 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> ~*k

   0  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

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

 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