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.

Sign up for GitHub

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

Jump to bottom

Disable ICU package for Apple mobile builds #107855

Merged
merged 1 commit into from
Sep 16, 2024

Disable ICU package for Apple mobile builds

b939cfd
Select commit
Loading
Failed to load commit list.
Merged

Disable ICU package for Apple mobile builds #107855

Disable ICU package for Apple mobile builds
b939cfd
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Sep 16, 2024 in 2h 30m 43s

Build #20240916.10 had test failures

4 errors / 5,058 warnings

Details

Tests

  • Failed: 7 (0.00%)
  • Passed: 3,863,535 (98.21%)
  • Other: 70,585 (1.79%)
  • Total: 3,934,127

Annotations

Check failure on line 44 in .packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24461.5/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24461.5/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L44 

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24461.5/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test System.Collections.ObjectModel.Tests.CollectionTests.Insert_ZeroIndex has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/5b5ad65f-899f-44da-8413-5b7ad5869042/workitems/System.Runtime.Tests/console

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

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

.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.24461.5\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Workloads-NoWebcil-ST-Wasm.Build.Tests.AspNetCore.SignalRClientTests in job 7513af3f-befa-44e4-8f66-917b9430316c has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/7513af3f-befa-44e4-8f66-917b9430316c/workitems/Workloads-NoWebcil-ST-Wasm.Build.Tests.AspNetCore.SignalRClientTests/console

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

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

.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.24461.5\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Workloads-ST-Wasm.Build.Tests.TestAppScenarios.MemoryTests in job 39606b6d-2187-421d-9664-f7bf4ecf0281 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/39606b6d-2187-421d-9664-f7bf4ecf0281/workitems/Workloads-ST-Wasm.Build.Tests.TestAppScenarios.MemoryTests/console

Check failure on line 44 in .packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24461.5/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24461.5/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L44 

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24461.5/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test System.Numerics.Tensors.Tests.TensorSpanTests.TensorExtensionsSpanInTOut<Single> has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/cf916f40-b861-4a3b-adca-1e2a35252477/workitems/System.Numerics.Tensors.Tests/console

Check failure on line 1 in System.Collections.ObjectModel.Tests.CollectionTests.Insert_ZeroIndex

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Collections.ObjectModel.Tests.CollectionTests.Insert_ZeroIndex 

System.NullReferenceException : Object reference not set to an instance of an object.
Raw output 
   at System.Runtime.DispatchResolve.FindImplSlotForCurrentType(MethodTable*, MethodTable*, UInt16, Boolean, UInt16*, MethodTable**) + 0x44
   at System.Runtime.DispatchResolve.FindInterfaceMethodImplementationTarget(MethodTable*, MethodTable*, UInt16, MethodTable**) + 0x64
   at System.Runtime.CachedInterfaceDispatch.RhResolveDispatchWorker(Object, Void*, DispatchCellInfo&) + 0x70
   at System.Runtime.CachedInterfaceDispatch.RhpCidResolve_Worker(Object, IntPtr) + 0x30
   at System.Collections.ObjectModel.Tests.CollectionTests.Insert_ZeroIndex() + 0x5c
   at System.Runtime!<BaseAddress>+0x153212c
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x10c

Check failure on line 1 in Wasm.Build.Tests.TestAppScenarios.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Wasm.Build.Tests.TestAppScenarios.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop 

System.Exception : Failed to launch browser after 3 attempts
Raw output 
   at Wasm.Build.Tests.BrowserRunner.SpawnBrowserAsync(String browserUrl, Boolean headless, Int32 timeout, Int32 maxRetries) in /_/src/mono/wasm/Wasm.Build.Tests/BrowserRunner.cs:line 140
   at Wasm.Build.Tests.BrowserRunner.RunAsync(ToolCommand cmd, String args, Boolean headless, Action`2 onConsoleMessage, Action`1 onServerMessage, Action`1 onError, Func`2 modifyBrowserUrl) in /_/src/mono/wasm/Wasm.Build.Tests/BrowserRunner.cs:line 155
   at Wasm.Build.Tests.BlazorWasmTestBase.BlazorRunTest(String runArgs, String workingDirectory, BlazorRunOptions runOptions) in /_/src/mono/wasm/Wasm.Build.Tests/Blazor/BlazorWasmTestBase.cs:line 202
   at Wasm.Build.Tests.BlazorWasmTestBase.BlazorRunTest(String runArgs, String workingDirectory, BlazorRunOptions runOptions) in /_/src/mono/wasm/Wasm.Build.Tests/Blazor/BlazorWasmTestBase.cs:line 229
   at Wasm.Build.Tests.TestAppScenarios.AppTestBase.RunSdkStyleApp(RunOptions options, BlazorRunHost host) in /_/src/mono/wasm/Wasm.Build.Tests/TestAppScenarios/AppTestBase.cs:line 130
   at Wasm.Build.Tests.TestAppScenarios.MemoryTests.AllocateLargeHeapThenRepeatedlyInterop() in /_/src/mono/wasm/Wasm.Build.Tests/TestAppScenarios/MemoryTests.cs:line 38
--- End of stack trace from previous location ---

Check failure on line 1 in Wasm.Build.Tests.TestAppScenarios.MemoryTests.RunSimpleAppWithProfiler

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Wasm.Build.Tests.TestAppScenarios.MemoryTests.RunSimpleAppWithProfiler 

System.Exception : Failed to launch browser after 3 attempts
Raw output 
   at Wasm.Build.Tests.BrowserRunner.SpawnBrowserAsync(String browserUrl, Boolean headless, Int32 timeout, Int32 maxRetries) in /_/src/mono/wasm/Wasm.Build.Tests/BrowserRunner.cs:line 140
   at Wasm.Build.Tests.BrowserRunner.RunAsync(ToolCommand cmd, String args, Boolean headless, Action`2 onConsoleMessage, Action`1 onServerMessage, Action`1 onError, Func`2 modifyBrowserUrl) in /_/src/mono/wasm/Wasm.Build.Tests/BrowserRunner.cs:line 155
   at Wasm.Build.Tests.BlazorWasmTestBase.BlazorRunTest(String runArgs, String workingDirectory, BlazorRunOptions runOptions) in /_/src/mono/wasm/Wasm.Build.Tests/Blazor/BlazorWasmTestBase.cs:line 202
   at Wasm.Build.Tests.BlazorWasmTestBase.BlazorRunTest(String runArgs, String workingDirectory, BlazorRunOptions runOptions) in /_/src/mono/wasm/Wasm.Build.Tests/Blazor/BlazorWasmTestBase.cs:line 229
   at Wasm.Build.Tests.TestAppScenarios.AppTestBase.RunSdkStyleApp(RunOptions options, BlazorRunHost host) in /_/src/mono/wasm/Wasm.Build.Tests/TestAppScenarios/AppTestBase.cs:line 130
   at Wasm.Build.Tests.TestAppScenarios.MemoryTests.RunSimpleAppWithProfiler() in /_/src/mono/wasm/Wasm.Build.Tests/TestAppScenarios/MemoryTests.cs:line 51
--- End of stack trace from previous location ---

Check failure on line 1 in Workloads-ST-Wasm.Build.Tests.TestAppScenarios.MemoryTests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Workloads-ST-Wasm.Build.Tests.TestAppScenarios.MemoryTests.WorkItemExecution 

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