Update SDK to 9.0 preview 4 #102604
Merged
Update SDK to 9.0 preview 4 #102604
Azure Pipelines / runtime
succeeded
May 27, 2024 in 1h 19m 29s
Build #20240524.42 had test failures
Details
- Failed: 3 (0.00%)
- Passed: 4,213,406 (98.06%)
- Other: 83,240 (1.94%)
- Total: 4,296,649
Annotations
Check failure on line 1 in WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
azure-pipelines / runtime
WasmTestOnChrome-ST-System.Security.Cryptography.Tests.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in GC\\Scenarios\\ServerModel\\servermodel\\servermodel.cmd
azure-pipelines / runtime
GC\\Scenarios\\ServerModel\\servermodel\\servermodel.cmd
Assert failure(PID 9332 [0x00002474], Thread: 9336 [0x2478]): new_current_total_committed_bookkeeping == current_total_committed_bookkeeping
CORECLR! WKS::gc_heap::verify_committed_bytes + 0x5A (0x6f88bffb)
CORECLR! WKS::gc_heap::plan_phase + 0x1F8E (0x6f884a02)
CORECLR! WKS::gc_heap::gc1 + 0x155 (0x6f87a721)
CORECLR! WKS::gc_heap::garbage_collect + 0x3E0 (0x6f87a545)
CORECLR! WKS::GCHeap::GarbageCollectGeneration + 0x242 (0x6f86a9ba)
CORECLR! WKS::gc_heap::trigger_gc_for_alloc + 0x40 (0x6f88b327)
CORECLR! WKS::gc_heap::try_allocate_more_space + 0x12F (0x6f88b53f)
CORECLR! WKS::gc_heap::allocate_more_space + 0x14 (0x6f86f289)
CORECLR! WKS::GCHeap::Alloc + 0x181 (0x6f869e81)
CORECLR! Alloc + 0x14E (0x6f632204)
File: D:\a\_work\1\s\src\coreclr\gc\gc.cpp:47394
Image: C:\h\w\C2A40A57\p\corerun.exe
Return code: 1
Raw output file: C:\h\w\C2A40A57\w\BDBE0A05\uploads\Reports\GC.Scenarios\ServerModel\servermodel\servermodel.output.txt
Raw output:
BEGIN EXECUTION
"C:\h\w\C2A40A57\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" servermodel.dll /numrequests:100
Using -776099009 as random seed
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:\cores since 5/24/2024 8:40:56 PM
Processing C:\cores\corerun.exe.9332.dmp
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe -c "$<C:\h\w\C2A40A57\t\tmpyy5z5g.tmp" -z "C:\cores\corerun.exe.9332.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.9332.dmp]
User Mini Dump File with Full Memory: Only application data is available
************* Path validation summary **************
Response Time (ms) Location
OK C:\h\w\C2A40A57\p\PDB
Symbol search path is: C:\h\w\C2A40A57\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: Fri May 24 20:41:05.000 2024 (UTC + 0:00)
System Uptime: 0 days 1:26:09.315
Process Uptime: 0 days 0:00:08.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.
(2474.2478): 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=02f7cea8 ebx=00000000 ecx=00000000 edx=00000000 esi=02f7ce58 edi=02f7cea8
eip=6f8ea5ee esp=02f7d18c ebp=02f7e224 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:
6f8ea5ee 5e pop esi
0:000> cdb: Reading initial command '$<C:\h\w\C2A40A57\t\tmpyy5z5g.tmp'
0:000> .load C:\Users\runner\.dotnet\sos\sos.dll
0:000> ~*k
. 0 Id: 2474.2478 Suspend: 0 Teb: 02caf000 Unfrozen
ChildEBP RetAddr
02f7d198 6f8eb35e coreclr!FailFastOnAssert+0x21
02f7e224 6f8eaa14 coreclr!_DbgBreakCheck+0x337
02f7e294 6f8ead56 coreclr!_DbgBreakCheckNoThrow+0x51
02f7e328 6f88bffb coreclr!DbgAssertDialog+0x1ff
02f7e36c 6f884a02 coreclr!WKS::gc_heap::verify_committed_bytes+0x5a
02f7e518 6f87a721 coreclr!WKS::gc_hea
Raw output
at GC_Scenarios._ServerModel_servermodel_servermodel_._ServerModel_servermodel_servermodel_cmd()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
Check failure on line 1 in PayloadGroup0.WorkItemExecution
azure-pipelines / runtime
PayloadGroup0.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Loading