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

Fix RhpLockCmpXchg64 FCall on win-x86 #100155

Merged
merged 1 commit into from
Mar 22, 2024

Fix RhpLockCmpXchg64 FCall on win-x86

82d7937
Select commit
Loading
Failed to load commit list.
Merged

Fix RhpLockCmpXchg64 FCall on win-x86 #100155

Fix RhpLockCmpXchg64 FCall on win-x86
82d7937
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Mar 22, 2024 in 3h 8m 27s

Build #20240322.73 had test failures

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 1,042,875 (98.48%)
  • Other: 16,045 (1.52%)
  • Total: 1,058,922

Annotations

Check failure on line 24 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L24

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

Check failure on line 25 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L25

The operation was canceled.

Check failure on line 91 in .packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24165.6\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24165.6\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24165.6\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item PayloadGroup0 in job cc6bf88e-57ad-4e52-abcf-c92d30c69d6e has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/cc6bf88e-57ad-4e52-abcf-c92d30c69d6e/workitems/PayloadGroup0/console

Check failure on line 1 in GC\\API\\NoGCRegion\\Callback_Svr\\Callback_Svr.cmd

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

GC\\API\\NoGCRegion\\Callback_Svr\\Callback_Svr.cmd

Assert failure(PID 8336 [0x00002090], Thread: 8396 [0x20cc]): promoted_bytes (heap_number) == promoted

CORECLR! SVR::gc_heap::mark_phase + 0x167C (0x00007ffd`a7474ebc)
CORECLR! SVR::gc_heap::gc1 + 0x240 (0x00007ffd`a7466c40)
CORECLR! SVR::gc_heap::garbage_collect + 0x99B (0x00007ffd`a74669ab)
CORECLR! SVR::gc_heap::gc_thread_function + 0x504 (0x00007ffd`a7468354)
CORECLR! SVR::gc_heap::gc_thread_stub + 0x7E (0x00007ffd`a74687fe)
CORECLR! <lambda_a690b9153e88e2796aa895961dd0b6c1>::<lambda_invoker_cdecl> + 0x74 (0x00007ffd`a712fe14)
KERNEL32! BaseThreadInitThunk + 0x14 (0x00007ffd`d71b84d4)
NTDLL! RtlUserThreadStart + 0x21 (0x00007ffd`d99e1791)
    File: D:\a\_work\1\s\src\coreclr\gc\gc.cpp:24234
    Image: C:\h\w\C3A50A71\p\corerun.exe


Return code:      1
Raw output file:      C:\h\w\C3A50A71\w\A242094B\uploads\Reports\GC.API\NoGCRegion\Callback_Svr\Callback_Svr.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\C3A50A71\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  Callback_Svr.dll 
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:\cores since 3/22/2024 9:40:01 PM
Processing C:\cores\corerun.exe.8336.dmp
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe -c "$<C:\h\w\C3A50A71\t\tmpdcazna.tmp" -z "C:\cores\corerun.exe.8336.dmp"
stdout: 
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\h\w\C3A50A71\p\PDB
Symbol search path is: C:\h\w\C3A50A71\p\PDB
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 Mar 22 21:40:06.000 2024 (UTC + 0:00)
System Uptime: 0 days 0:19:39.134
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.
(2090.20cc): 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
KERNELBASE!RaiseFailFastException+0xae:
00007ffd`d69a96ce 803d4d78120000  cmp     byte ptr [KERNELBASE!local_unwind+0x7fe2 (00007ffd`d6ad0f22)],0 ds:00007ffd`d6ad0f22=00
0:006> cdb: Reading initial command '$<C:\h\w\C3A50A71\t\tmpdcazna.tmp'
0:006> .load C:\Users\runner\.dotnet\sos\sos.dll
0:006> ~*k

   0  Id: 2090.2094 Suspend: 0 Teb: 00000022`531f6000 Unfrozen
Child-SP          RetAddr           Call Site
00000022`5337d7a8 00007ffd`d6906d1f ntdll!ZwWaitForSingleObject+0x14
00000022`5337d7b0 00007ffd`a748efc2 KERNELBASE!WaitForSingleObjectEx+0x8f
00000022`5337d850 00007ffd`a7444929 coreclr!SVR::gc_heap::wait_for_gc_done+0x1b2
00000022`5337d8b0 00007ffd`a748a921 coreclr!SVR::GCHeap::GarbageCollectGeneration+0x359
00000022`5337d900 00007ffd`a7443430 coreclr!SVR::gc_heap::trigger_gc_for_alloc+0x71
(Inline Function) --------`-------- coreclr!SVR::gc_heap::try_allocate_more_space+0xca
(Inline Function) --------`-------- coreclr!SVR::gc_h
Raw output
   at GC_API._NoGCRegion_Callback_Svr_Callback_Svr_._NoGCRegion_Callback_Svr_Callback_Svr_cmd()
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Check failure on line 1 in PayloadGroup0.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines 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.