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

Don't run trim-unfriendly ConcurrentDictionary test #108925

Merged
merged 1 commit into from
Oct 17, 2024

Thankless janitorial work

a37c700
Select commit
Loading
Failed to load commit list.
Merged

Don't run trim-unfriendly ConcurrentDictionary test #108925

Thankless janitorial work
a37c700
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime cancelled Oct 16, 2024 in 1h 52m 53s

Build #20241016.10 had test failures

3 errors / 23 warnings

Details

Tests

  • Failed: 3 (0.00%)
  • Passed: 2,708,716 (98.23%)
  • Other: 48,732 (1.77%)
  • Total: 2,757,451

Annotations

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

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24504.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-ST-System.Net.Http.Functional.Tests in job 7dbd6438-f9ea-4394-9e97-f24c42c414bb has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/7dbd6438-f9ea-4394-9e97-f24c42c414bb/workitems/WasmTestOnChrome-ST-System.Net.Http.Functional.Tests/console

Check failure on line 1 in System.Net.Http.Functional.Tests.TelemetryTest_Http11.EventSource_ExistsWithCorrectId

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Net.Http.Functional.Tests.TelemetryTest_Http11.EventSource_ExistsWithCorrectId 

Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: "System.Net.Http"
Actual:   "HttpTelemetry"
           ↑ (pos 0)
Raw output 
   at System.Net.Http.Functional.Tests.TelemetryTest.EventSource_ExistsWithCorrectId()
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object , BindingFlags )

Check failure on line 1 in System.Net.Http.Functional.Tests.TelemetryTest_Http20.EventSource_ExistsWithCorrectId

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Net.Http.Functional.Tests.TelemetryTest_Http20.EventSource_ExistsWithCorrectId 

Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: "System.Net.Http"
Actual:   "HttpTelemetry"
           ↑ (pos 0)
Raw output 
   at System.Net.Http.Functional.Tests.TelemetryTest.EventSource_ExistsWithCorrectId()
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object , BindingFlags )

Check failure on line 1 in WasmTestOnChrome-ST-System.Net.Http.Functional.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-ST-System.Net.Http.Functional.Tests.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