.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24311.10\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item PayloadGroup0 in job 21769334-a6b0-4a40-b9a8-5857e967905a has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/21769334-a6b0-4a40-b9a8-5857e967905a/workitems/PayloadGroup0/console

.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24311.10\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize_SynchronizingObject has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/39ccece3-2a8d-4854-802b-2b187de10f2e/workitems/System.IO.FileSystem.Watcher.Tests/console

The Operation will be canceled. The next steps may not contain expected logs.

Assert failure(PID 7668 [0x00001df4], Thread: 8240 [0x2030]): new_current_total_committed_bookkeeping == current_total_committed_bookkeeping

CORECLR! WKS::gc_heap::verify_committed_bytes + 0x5A (0x709e30f8)
CORECLR! WKS::gc_heap::plan_phase + 0x1F8B (0x709dbb00)
CORECLR! WKS::gc_heap::gc1 + 0x155 (0x709d1814)
CORECLR! WKS::gc_heap::garbage_collect + 0x3E0 (0x709d1638)
CORECLR! WKS::GCHeap::GarbageCollectGeneration + 0x242 (0x709c1aba)
CORECLR! WKS::gc_heap::trigger_gc_for_alloc + 0x40 (0x709e2427)
CORECLR! WKS::gc_heap::try_allocate_more_space + 0x12F (0x709e263f)
CORECLR! WKS::gc_heap::allocate_more_space + 0x14 (0x709c6389)
CORECLR! WKS::GCHeap::Alloc + 0x181 (0x709c0f81)
CORECLR! Alloc + 0x14E (0x7078de94)
    File: D:\a\_work\1\s\src\coreclr\gc\gc.cpp:47405
    Image: C:\h\w\9FB408C7\p\corerun.exe


Return code:      1
Raw output file:      C:\h\w\9FB408C7\w\A5DD0978\uploads\Reports\GC.Scenarios\SingLinkList\singlinkstay\singlinkstay.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\9FB408C7\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  singlinkstay.dll 
Test should return with ExitCode 100 ...
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:\cores since 6/18/2024 7:34:37 PM
Processing C:\cores\corerun.exe.7668.dmp
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe -c "$<C:\h\w\9FB408C7\t\tmpawsegv.tmp" -z "C:\cores\corerun.exe.7668.dmp"
stdout: 
Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\cores\corerun.exe.7668.dmp]
User Mini Dump File with Full Memory: Only application data is available


************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\h\w\9FB408C7\p\PDB
Symbol search path is: C:\h\w\9FB408C7\p\PDB
Executable search path is: 
Windows 10 Version 14393 MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer DataCenter SingleUserTS
10.0.14393.6343 (rs1_release.230913-1727)
Machine Name:
Debug session time: Tue Jun 18 19:34:42.000 2024 (UTC + 0:00)
System Uptime: 0 days 4:18:36.130
Process Uptime: 0 days 0:00:05.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.
(1df4.2030): Unknown exception - code c0000602 (first/second chance not available)
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for coreclr.dll
eax=0077ccc0 ebx=00000000 ecx=00000000 edx=00000000 esi=0077cc70 edi=0077ccc0
eip=70a413f1 esp=0077cfa4 ebp=0077e03c iopl=0         nv up ei pl nz ac po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000212
coreclr!FailFastOnAssert+0x21:
70a413f1 5e              pop     esi
0:000> cdb: Reading initial command '$<C:\h\w\9FB408C7\t\tmpawsegv.tmp'
0:000> .load C:\Users\runner\.dotnet\sos\sos.dll
0:000> ~*k

.  0  Id: 1df4.2030 Suspend: 0 Teb: 0051b000 Unfrozen
ChildEBP RetAddr  
0077cfb0 70a42161 coreclr!FailFastOnAssert+0x21
0077e03c 70a41817 coreclr!_DbgBreakCheck+0x337
0077e0ac 70a41b59 coreclr!_DbgBreakCheckNoThrow+0x51
0077e140 709e30f8 coreclr!DbgAssertDialog+0x1ff
0077e184 709dbb00 coreclr!WKS::gc_heap::verify_committed_bytes+0x5a
0077e330 709d1814 coreclr!WKS::gc_heap::p

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

Did not observe an error event within 500ms and 3 attempts.

cmdLine:C:\h\w\9A910891\w\A7C90932\e\GC\Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.cmd Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 6/18/2024 6:56:46 PM, end: 6/18/2024 7:06:46 PM)

Return code:      -100
Raw output file:      C:\h\w\9A910891\w\A7C90932\uploads\Reports\GC.Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\9A910891\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  FinalizeTimeout.dll 
Main start
Finalizer start
Finalizer end
Main end

cmdLine:C:\h\w\9A910891\w\A7C90932\e\GC\Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.cmd Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 6/18/2024 6:56:46 PM, end: 6/18/2024 7:06:46 PM)
Test Harness Exitcode is : -100
To run the test:
> set CORE_ROOT=C:\h\w\9A910891\p
> C:\h\w\9A910891\w\A7C90932\e\GC\Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.cmd