Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JIT: Remove unnecessary argument and fix a JITDUMP format string #105074

Merged
merged 2 commits into from
Jul 18, 2024

Run jit-format

9dc2248
Select commit
Loading
Failed to load commit list.
Merged

JIT: Remove unnecessary argument and fix a JITDUMP format string #105074

Run jit-format
9dc2248
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Jul 18, 2024 in 0s

.NET Result Analysis

Details

⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis

All checks completed

[runtime]

[runtime-dev-innerloop]

Build Rerun

✔️ Build passed after 1 retries.

(Attempt #1) [link to build]

runtime / Build / coreclr Pri0 Runtime Tests Run windows x86 checked / Send tests to Helix (Windows)

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24360.4\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item PayloadGroup0 in job 2ddd53bb-4fa9-48c6-b81a-aded7ea257dd has failed. [Failure log]

Non-Deterministic Test Failures Detected

GC\\Regressions\\v2.0-beta2\\460373\\460373\\460373.cmd [Console] [Details] [Artifacts] [0.28% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

Failing Configuration

Exception Message
Assert failure(PID 10184 [0x000027c8], Thread: 10188 [0x27cc]): new_current_total_committed_bookkeeping == current_total_committed_bookkeeping

CORECLR! WKS::gc_heap::verify_committed_bytes + 0x5A (0x7066c0d4)
CORECLR! WKS::gc_heap::plan_phase + 0x1F8B (0x70664abe)
CORECLR! WKS::gc_heap::gc1 + 0x155 (0x7065a791)
CORECLR! WKS::gc_heap::garbage_collect + 0x3E0 (0x7065a5b5)
CORECLR! WKS::GCHeap::GarbageCollectGeneration + 0x24C (0x7064a954)
CORECLR! WKS::gc_heap::trigger_gc_for_alloc + 0x40 (0x7066b3f9)
CORECLR! WKS::gc_heap::try_allocate_more_space + 0x12F (0x7066b611)
CORECLR! WKS::gc_heap::allocate_more_space + 0x14 (0x7064f239)
CORECLR! WKS::GCHeap::Alloc + 0x185 (0x70649bd5)
CORECLR! Alloc + 0x147 (0x7041cafa)
File: D:\a\_work\1\s\src\coreclr\gc\gc.cpp:47452
Image: C:\h\w\C1250A95\p\corerun.exe

Return code: 1
Raw output file: C:\h\w\C1250A95\w\A10E0869\uploads\Reports\GC.Regressions\v2.0-beta2\460373\460373\460373.output.txt
Raw output:
BEGIN EXECUTION
"C:\h\w\C1250A95\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" 460373.dll
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:\cores since 7/18/2024 10:58:07 AM
Processing C:\cores\corerun.exe.10184.dmp
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe -c "$<C:\h\w\C1250A95\t\tmphdjxbs.tmp" -z "C:\cores\corerun.exe.10184.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.10184.dmp]
User Mini Dump File with Full Memory: Only application data is available

************* Path validation summary **************
Response Time (ms) Location
OK C:\h\w\C1250A95\p\PDB
Symbol search path is: C:\h\w\C1250A95\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: Thu Jul 18 10:58:13.000 2024 (UTC + 0:00)
System Uptime: 0 days 0:49:58.387
Process Uptime: 0 days 0:00:06.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.
(27c8.27cc): 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=0337d220 ebx=00000000 ecx=00000000 edx=00000000 esi=0337d1d0 edi=0337d220
eip=706cabb9 esp=0337d500 ebp=0337e58c iopl=0 nv up ei pl nz ac pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000216
coreclr!FailFastOnAssert+0x21:
706cabb9 5e pop esi
0:000> cdb: Reading initial command '$<C:\h\w\C1250A95\t\tmphdjxbs.tmp'
0:000> .load C:\Users\runner\.dotnet\sos\sos.dll
0:000> ~*k

. 0 Id: 27c8.27cc Suspend: 0 Teb: 030e2000 Unfrozen
ChildEBP RetAddr
0337d50c 706cb929 coreclr!FailFastOnAssert+0x21
0337e58c 706cafdf coreclr!_DbgBreakCheck+0x337
0337e5f0 706cb321 coreclr!_DbgBreakCheckNoThrow+0x51
0337e670 7066c0d4 coreclr!DbgAssertDialog+0x1ff
0337e6b4 70664abe coreclr!WKS::gc_heap::verify_committed_bytes+0x5a
0337e850 7065a791 coreclr!WKS::gc_heap::plan_phase+0x1f8b
0337e874 7065a5b5 coreclr!WKS::gc

CallStack
   at GC_Regressions._v2_0_beta2_460373_460373_460373_._v2_0_beta2_460373_460373_460373_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)
PayloadGroup0.WorkItemExecution [Console] [Details] [Artifacts] [4.59% 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

Was this helpful? Yes No