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

Update SVE instructions that writes to GC regs #112389

Merged
merged 1 commit into from
Feb 12, 2025

Update SVE instructions that writes to GC regs

539d02a
Select commit
Loading
Failed to load commit list.
Merged

Update SVE instructions that writes to GC regs #112389

Update SVE instructions that writes to GC regs
539d02a
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime-coreclr gcstress0x3-gcstress0xc failed Feb 11, 2025 in 7h 12m 7s

Build #20250211.1 had test failures

Details

Tests

  • Failed: 14 (0.00%)
  • Passed: 247,189 (26.06%)
  • Other: 701,487 (73.94%)
  • Total: 948,690

Annotations

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

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

.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.25106.4\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Loader.1.3 in job 4af1b3d5-9f03-421b-be10-706394e86c84 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/4af1b3d5-9f03-421b-be10-706394e86c84/workitems/Loader.1.3/console

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

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

.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.25106.4\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item LoaderClassloaderGenerics.0.1 in job 4af1b3d5-9f03-421b-be10-706394e86c84 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/4af1b3d5-9f03-421b-be10-706394e86c84/workitems/LoaderClassloaderGenerics.0.1/console

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

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

.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.25106.4\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Regression_1.0.4 in job 4af1b3d5-9f03-421b-be10-706394e86c84 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/4af1b3d5-9f03-421b-be10-706394e86c84/workitems/Regression_1.0.4/console

Check failure on line 1 in baseservices/callconvs/TestCallingConventions/TestCallingConventions.cmd

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

baseservices/callconvs/TestCallingConventions/TestCallingConventions.cmd

Assert failure(PID 884 [0x00000374], Thread: 4164 [0x1044]): !CREATE_CHECK_STRING(pMT && pMT->Validate())

CORECLR! Object::ValidateInner + 0x11A (0x00007ffc`2f417a3a)
CORECLR! Object::Validate + 0xA1 (0x00007ffc`2f4178e1)
CORECLR! GcInfoDecoder::ReportStackSlotToGC + 0x139 (0x00007ffc`2f864d19)
CORECLR! GcInfoDecoder::ReportSlotToGC + 0x1EA (0x00007ffc`2f864bba)
CORECLR! GcInfoDecoder::EnumerateLiveSlots + 0x9C1 (0x00007ffc`2f862531)
CORECLR! EECodeManager::EnumGcRefs + 0x2A1 (0x00007ffc`2f2e4071)
CORECLR! GcStackCrawlCallBack + 0x52A (0x00007ffc`2f5b14ba)
CORECLR! Thread::StackWalkFramesEx + 0x268 (0x00007ffc`2f47e818)
CORECLR! Thread::StackWalkFrames + 0x16D (0x00007ffc`2f47e50d)
CORECLR! ScanStackRoots + 0x24D (0x00007ffc`2f5ae04d)
    File: D:_work1ssrccoreclrmobject.cpp:560
    Image: C:hwAD8708C6pcorerun.exe


Return code:      1
Raw output file:      C:hwAD8708C6wB07F094CuploadscallconvsTestCallingConventionsoutput.txt
Raw output:
BEGIN EXECUTION
 "C:hwAD8708C6pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  TestCallingConventions.dll 
Running BlittableFunctionPointers...
 -- unmanaged
 -- unmanaged cdecl
 -- unmanaged stdcall
 -- unmanaged modopt(cdecl)
 -- unmanaged modopt(stdcall)
 -- unmanaged modopt unrecognized
 -- unmanaged modopt(stdcall) modopt(cdecl)
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:cores since 2/11/2025 3:53:52 PM
Processing C:corescorerun.exe.884.dmp
Invoking: C:Program Files (x86)Windows Kits10Debuggersdcdb.exe -c "$<C:hwAD8708C6		mpje3i1e.tmp" -z "C:corescorerun.exe.884.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.884.dmp]
User Mini Dump File with Full Memory: Only application data is available


************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:hwAD8708C6pPDB
Symbol search path is: C:hwAD8708C6pPDB
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: Tue Feb 11 15:53:57.000 2025 (UTC + 0:00)
System Uptime: 0 days 0:13:51.075
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.
(374.1044): 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:
00007ffc`5ade973e 803ddd77120000  cmp     byte ptr [KERNELBASE!local_unwind+0x75f2 (00007ffc`5af10f22)],0 ds:00007ffc`5af10f22=00
0:000> cdb: Reading initial command '$<C:hwAD8708C6		mpje3i1e.tmp'
0:000> .load C:Users
unner.dotnetsossos.dll
0:000> ~*k

.  0  Id: 374.1044 Suspend: 0 Teb: 00000017`91f47000 Unfrozen
Child-SP          RetAddr           Call Site
00000017`91db8a20 00007ffc`2f98bc0b KERNELBASE!RaiseFailFastException+0xae
00000017`91db8ff0 00007ffc`2f98b4d5 coreclr!_DbgBreakCheck+0x2eb
00000017`91dba140 00007ffc`2f98b6cd coreclr!_DbgBreakCheckNoThrow+0x55
00000017`91dba1e0 00007ffc`2f417a3a coreclr!DbgAssertDialog+0x19d
00000017`91dba2d0 00007ffc`2f4178e1 coreclr!Object::ValidateInner+0x11a
00000017`9
Raw output
   at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 141
   at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
   at Program.<<Main>$>g__TestExecutor4|0_5(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)

Check failure on line 1 in Interop.0.1.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

Interop.0.1.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 JIT.opt.0.1.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

JIT.opt.0.1.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 Loader.0.3.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr gcstress0x3-gcstress0xc

Loader.0.3.WorkItemExecution

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