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

[release/8.0] [JIT] ARM64 - Temporary fix for ldp/stp optimizations - with test fix #90758

Merged
merged 7 commits into from
Aug 17, 2023

Fixing test again...

8151e86
Select commit
Loading
Failed to load commit list.
Merged

[release/8.0] [JIT] ARM64 - Temporary fix for ldp/stp optimizations - with test fix #90758

Fixing test again...
8151e86
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Aug 17, 2023 in 3h 9m 11s

Build #20230817.56 had test failures

Details

Tests

  • Failed: 4 (0.00%)
  • Passed: 1,068,350 (98.45%)
  • Other: 16,853 (1.55%)
  • Total: 1,085,207

Annotations

Check failure on line 89 in .packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23415.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23415.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L89

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23415.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(89,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item PayloadGroup0 in job dea043f3-3f50-4910-95e0-06f082e6600f has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/dea043f3-3f50-4910-95e0-06f082e6600f/workitems/PayloadGroup0/console

Check failure on line 89 in .packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23415.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23415.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L89

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23415.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(89,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item PayloadGroup0 in job 22ed00cf-44e0-47b1-ae63-f0ff67cd0d0b has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/22ed00cf-44e0-47b1-ae63-f0ff67cd0d0b/workitems/PayloadGroup0/console

Check failure on line 1 in Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh

[createdump] Invalid process id: task_for_pid(16351) FAILED (os/kern) failure (5)
[createdump] This failure may be because createdump or the application is not properly signed and entitled.
[createdump] Failure took 0ms
waitpid() returned successfully (wstatus 0000ff00) WEXITSTATUS ff WTERMSIG 0
/private/tmp/helix/working/A87408DB/w/AAF70944/e/Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh: line 454: 16351 Segmentation fault: 11  (core dumped) $LAUNCHER $ExePath "${CLRTestExecutionArguments[@]}"

Return code:      1
Raw output file:      /tmp/helix/working/A87408DB/w/AAF70944/uploads/Reports/Loader.binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.output.txt
Raw output:
BEGIN EXECUTION
/tmp/helix/working/A87408DB/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true BinderTracingTest.ResolutionFlow.dll ''
[12:54:20 PM] Running AssemblyLoadContextResolving_ReturnNull...
[12:54:21 PM] Running AssemblyLoadContextResolving_LoadAssembly...
[12:54:21 PM] Running AssemblyLoadContextResolving_NameMismatch...
[12:54:21 PM] Running AssemblyLoadContextResolving_MultipleHandlers...
[12:54:22 PM] Running AppDomainAssemblyResolve_ReturnNull...
[12:54:22 PM] Running AppDomainAssemblyResolve_LoadAssembly...
[12:54:22 PM] Running AppDomainAssemblyResolve_NameMismatch...
[12:54:22 PM] Running AppDomainAssemblyResolve_MultipleHandlers...
[12:54:22 PM] Launching process for AssemblyLoadFromResolveHandler_LoadDependency...
[createdump] Target process is alive
Expected: 100
Actual: 139
END EXECUTION - FAILED
Test failed. Trying to see if dump file was created in /cores since 8/17/2023 12:54:20 PM
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=/tmp/helix/working/A87408DB/p
> /private/tmp/helix/working/A87408DB/w/AAF70944/e/Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh
Expected: True
Actual:   False
Raw output
   at Loader_binding._tracing_BinderTracingTest_ResolutionFlow_BinderTracingTest_ResolutionFlow_._tracing_BinderTracingTest_ResolutionFlow_BinderTracingTest_ResolutionFlow_sh()
   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.

Check failure on line 1 in Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh

[createdump] Invalid process id: task_for_pid(68151) FAILED (os/kern) failure (5)
[createdump] This failure may be because createdump or the application is not properly signed and entitled.
[createdump] Failure took 0ms
waitpid() returned successfully (wstatus 0000ff00) WEXITSTATUS ff WTERMSIG 0
/private/tmp/helix/working/B25D09F1/w/99A50870/e/Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh: line 445: 68151 Segmentation fault: 11  (core dumped) $LAUNCHER $ExePath "${CLRTestExecutionArguments[@]}"

Return code:      1
Raw output file:      /tmp/helix/working/B25D09F1/w/99A50870/uploads/Reports/Loader.binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.output.txt
Raw output:
BEGIN EXECUTION
/tmp/helix/working/B25D09F1/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true BinderTracingTest.ResolutionFlow.dll ''
[12:54:58 PM] Running AssemblyLoadContextResolving_ReturnNull...
[12:54:58 PM] Running AssemblyLoadContextResolving_LoadAssembly...
[12:54:59 PM] Running AssemblyLoadContextResolving_NameMismatch...
[12:54:59 PM] Running AssemblyLoadContextResolving_MultipleHandlers...
[12:54:59 PM] Running AppDomainAssemblyResolve_ReturnNull...
[12:54:59 PM] Running AppDomainAssemblyResolve_LoadAssembly...
[12:54:59 PM] Running AppDomainAssemblyResolve_NameMismatch...
[12:55:00 PM] Running AppDomainAssemblyResolve_MultipleHandlers...
[12:55:00 PM] Launching process for AssemblyLoadFromResolveHandler_LoadDependency...
[createdump] Target process is alive
Expected: 100
Actual: 139
END EXECUTION - FAILED
Test failed. Trying to see if dump file was created in /cores since 8/17/2023 12:54:58 PM
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=/tmp/helix/working/B25D09F1/p
> /private/tmp/helix/working/B25D09F1/w/99A50870/e/Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.sh
Expected: True
Actual:   False
Raw output
   at Loader_binding._tracing_BinderTracingTest_ResolutionFlow_BinderTracingTest_ResolutionFlow_._tracing_BinderTracingTest_ResolutionFlow_BinderTracingTest_ResolutionFlow_sh()
   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.