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

Normalize the creation of simd comparison nodes and give basic constant folding support #104215

Merged
merged 5 commits into from
Jul 3, 2024

Fixing a test that was checking disassembly

d033e8b
Select commit
Loading
Failed to load commit list.
Merged

Normalize the creation of simd comparison nodes and give basic constant folding support #104215

Fixing a test that was checking disassembly
d033e8b
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime succeeded Jul 1, 2024 in 42m 43s

Build #20240701.3 had test failures

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 1,186,777 (98.32%)
  • Other: 20,262 (1.68%)
  • Total: 1,207,041

Annotations

Check failure on line 1 in GC\\Scenarios\\DoublinkList\\dlstack\\dlstack.cmd

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

GC\\Scenarios\\DoublinkList\\dlstack\\dlstack.cmd

Assert failure(PID 2860 [0x00000b2c], Thread: 2828 [0x0b0c]): new_current_total_committed_bookkeeping == current_total_committed_bookkeeping

CORECLR! WKS::gc_heap::verify_committed_bytes + 0x5A (0x7068e7e4)
CORECLR! WKS::gc_heap::plan_phase + 0x1F8B (0x706871cc)
CORECLR! WKS::gc_heap::gc1 + 0x155 (0x7067cea1)
CORECLR! WKS::gc_heap::garbage_collect + 0x3E0 (0x7067ccc5)
CORECLR! WKS::GCHeap::GarbageCollectGeneration + 0x24C (0x7066d064)
CORECLR! WKS::gc_heap::trigger_gc_for_alloc + 0x40 (0x7068db09)
CORECLR! WKS::gc_heap::try_allocate_more_space + 0x12F (0x7068dd21)
CORECLR! WKS::gc_heap::allocate_more_space + 0x14 (0x7067194d)
CORECLR! WKS::GCHeap::Alloc + 0x187 (0x7066c527)
CORECLR! Alloc + 0x147 (0x7043be8a)
    File: D:\a\_work\1\s\src\coreclr\gc\gc.cpp:47452
    Image: C:\h\w\B14E094D\p\corerun.exe


Return code:      1
Raw output file:      C:\h\w\B14E094D\w\AFD809AE\uploads\Reports\GC.Scenarios\DoublinkList\dlstack\dlstack.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\B14E094D\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  dlstack.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 7/1/2024 8:48:05 AM
Processing C:\cores\corerun.exe.2860.dmp
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe -c "$<C:\h\w\B14E094D\t\tmp04fhsy.tmp" -z "C:\cores\corerun.exe.2860.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.2860.dmp]
User Mini Dump File with Full Memory: Only application data is available


************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\h\w\B14E094D\p\PDB
Symbol search path is: C:\h\w\B14E094D\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: Mon Jul  1 08:48:11.000 2024 (UTC + 0:00)
System Uptime: 0 days 2:12:12.525
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.
(b2c.b0c): 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=0057ce18 ebx=00000000 ecx=00000000 edx=00000000 esi=0057cdc8 edi=0057ce18
eip=706ed2d9 esp=0057d0f8 ebp=0057e184 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:
706ed2d9 5e              pop     esi
0:000> cdb: Reading initial command '$<C:\h\w\B14E094D\t\tmp04fhsy.tmp'
0:000> .load C:\Users\runner\.dotnet\sos\sos.dll
0:000> ~*k

.  0  Id: b2c.b0c Suspend: 0 Teb: 002b3000 Unfrozen
ChildEBP RetAddr  
0057d104 706ee04a coreclr!FailFastOnAssert+0x21
0057e184 706ed6ff coreclr!_DbgBreakCheck+0x337
0057e1e8 706eda41 coreclr!_DbgBreakCheckNoThrow+0x51
0057e268 7068e7e4 coreclr!DbgAssertDialog+0x1ff
0057e2ac 706871cc coreclr!WKS::gc_heap::verify_committed_bytes+0x5a
0057e448 7067cea1 coreclr!WKS::gc_heap::plan_phase+0x1f8b
0
Raw output
   at GC_Scenarios._DoublinkList_dlstack_dlstack_._DoublinkList_dlstack_dlstack_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

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.