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

Ensure GetElement are marked as having an immediate operand for Arm64 #104204

Merged
merged 2 commits into from
Jun 30, 2024

Ensure IsSafeToContainMem is checked

2834d0a
Select commit
Loading
Failed to load commit list.
Merged

Ensure GetElement are marked as having an immediate operand for Arm64 #104204

Ensure IsSafeToContainMem is checked
2834d0a
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime succeeded Jun 30, 2024 in 44m 2s

Build #20240629.39 had test failures

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 1,119,641 (98.43%)
  • Other: 17,869 (1.57%)
  • Total: 1,137,512

Annotations

Check failure on line 1 in GC\\Scenarios\\FinalizeTimeout\\FinalizeTimeout\\FinalizeTimeout.cmd

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

GC\\Scenarios\\FinalizeTimeout\\FinalizeTimeout\\FinalizeTimeout.cmd

cmdLine:C:\h\w\A6130927\w\B31F0955\e\GC\Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.cmd Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 6/30/2024 5:24:48 AM, end: 6/30/2024 5:34:48 AM)

Return code:      -100
Raw output file:      C:\h\w\A6130927\w\B31F0955\uploads\Reports\GC.Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\A6130927\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  FinalizeTimeout.dll 
Main start
Finalizer start
Finalizer end
Main end

cmdLine:C:\h\w\A6130927\w\B31F0955\e\GC\Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.cmd Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout, start: 6/30/2024 5:24:48 AM, end: 6/30/2024 5:34:48 AM)
Test Harness Exitcode is : -100
To run the test:
> set CORE_ROOT=C:\h\w\A6130927\p
> C:\h\w\A6130927\w\B31F0955\e\GC\Scenarios\FinalizeTimeout\FinalizeTimeout\FinalizeTimeout.cmd
Raw output
   at GC_Scenarios._FinalizeTimeout_FinalizeTimeout_FinalizeTimeout_._FinalizeTimeout_FinalizeTimeout_FinalizeTimeout_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.