Skip to content

Update dependencies from https://github.com/dotnet/cecil build 202402…

Azure Pipelines / runtime failed Feb 15, 2024 in 1h 50m 30s

Build #20240215.34 had test failures

Details

Tests

  • Failed: 3 (0.00%)
  • Passed: 3,551,669 (98.19%)
  • Other: 65,628 (1.81%)
  • Total: 3,617,300

Annotations

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24112.1/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.24112.1/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24112.1/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item profiler.multiple in job 1054f50b-57a7-4f92-93ad-b584c4d9442d has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/1054f50b-57a7-4f92-93ad-b584c4d9442d/workitems/profiler.multiple/console

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24112.1/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.24112.1/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24112.1/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests in job 7ffb5841-76ed-49df-bff2-54b88594efbe has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/7ffb5841-76ed-49df-bff2-54b88594efbe/workitems/WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests/console

Check failure on line 1 in WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.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 profiler/multiple/multiple/multiple.sh

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

profiler/multiple/multiple/multiple.sh

Unhandled exception. System.Exception: Profilee returned exit code 139 instead of expected exit code 100.
   at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error)
   at Profiler.Tests.ProfilerTestRunner.Run(String profileePath, String testName, Guid profilerClsid, String profileeArguments, ProfileeOptions profileeOptions, Dictionary`2 envVars, String reverseServerName, Boolean loadAsNotification, Int32 notificationCopies)
   at Profiler.Tests.MultiplyLoaded.Main(String[] args)
/root/helix/work/workitem/e/profiler/multiple/multiple/multiple.sh: line 454:    38 Aborted                 (core dumped) $LAUNCHER $ExePath "${CLRTestExecutionArguments[@]}"

Return code:      1
Raw output file:      /root/helix/work/workitem/uploads/Reports/profiler.multiple/multiple/multiple.output.txt
Raw output:
BEGIN EXECUTION
/root/helix/work/correlation/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true multiple.dll ''
Profiler path: /root/helix/work/workitem/e/profiler/multiple/multiple/libProfiler.so
Profiler path: /root/helix/work/workitem/e/profiler/multiple/multiple/libProfiler.so
Profiler.dll!DllGetClassObject
Profiler.dll!Profiler::Initialize
Setting exception mask
Profiler.dll!DllGetClassObject
Profiler.dll!Profiler::Initialize
Profiler path: /root/helix/work/workitem/e/profiler/multiple/multiple/libProfiler.so
Setting exception mask
MultiplyLoaded::ExceptionThrown, number seen = 0
MultiplyLoaded::ExceptionThrown, number seen = 1
Requesting detach!!
RequestProfilerDetach hr=0x0
Requesting detach!!
ProfilerDetachSucceeded _detachCount=1
RequestProfilerDetach hr=0x0
Profiler.dll!DllGetClassObject
ProfilerDetachSucceeded _detachCount=2
PROFILER TEST PASSES
Profiler.dll!Profiler::Initialize
Throwing exception
Exception caught
Waiting for profilers to all detach
Setting exception mask
MultiplyLoaded::ExceptionThrown, number seen = 2
Profiler.dll!Profiler::Shutdown

Test failed: Profilee returned exit code 139 instead of expected exit code 100.
Expected: 100
Actual: 134
END EXECUTION - FAILED
Test failed. Trying to see if dump file was created in /home/helixbot/dotnetbuild/dumps since 2/15/2024 3:18:17 PM
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=/root/helix/work/correlation
> /root/helix/work/workitem/e/profiler/multiple/multiple/multiple.sh
Raw output
   at profiler_multiple._multiple_multiple_._multiple_multiple_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 profiler.multiple.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

profiler.multiple.WorkItemExecution

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