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

[Test] For named mutexes, check if Windows Nano Server uses different namespaces when using Local\ and Global\ prefixes #112266

Closed
wants to merge 1 commit into from

fix

62f892b
Select commit
Loading
Failed to load commit list.
Closed

[Test] For named mutexes, check if Windows Nano Server uses different namespaces when using Local\ and Global\ prefixes #112266

fix
62f892b
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Feb 7, 2025 in 2h 25m 33s

Build #20250207.9 had test failures

6 errors / 6 warnings

Details

Tests

  • Failed: 6 (0.00%)
  • Passed: 3,069,150 (98.20%)
  • Other: 56,196 (1.80%)
  • Total: 3,125,352

Annotations

Check failure on line 44 in .packages\microsoft.dotnet.helix.sdk\10.0.0-beta.25080.7\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.25080.7\tools\azure-pipelines\AzurePipelines.MultiQueue.targets#L44 

.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.25080.7\tools\azure-pipelines\AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test System.Threading.Tests.MutexTests.CheckWhichWindowsVersionsDistinguishLocalAndGlobalNamespaces has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/4a9ced2a-3b1f-4453-addd-4d500c6f2323/workitems/System.Threading.Tests/console

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

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25080.7/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.Threading.Tasks.Tests in job 32008167-491d-475c-8e62-924849c2f25b has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/32008167-491d-475c-8e62-924849c2f25b/workitems/System.Threading.Tasks.Tests/console

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

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25080.7/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.Net.Http.Functional.Tests in job 7b1aea74-4e34-4684-891a-bd6e259267c8 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/7b1aea74-4e34-4684-891a-bd6e259267c8/workitems/WasmTestOnChrome-MT-System.Net.Http.Functional.Tests/console

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

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25080.7/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.Net.WebSockets.Client.Tests in job 7b1aea74-4e34-4684-891a-bd6e259267c8 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/7b1aea74-4e34-4684-891a-bd6e259267c8/workitems/WasmTestOnChrome-MT-System.Net.WebSockets.Client.Tests/console

Check failure on line 1 in System.Threading.Tasks.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Threading.Tasks.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 WasmTestOnChrome-ST-System.Runtime.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-MT-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.

Check failure on line 1 in WasmTestOnChrome-MT-System.Net.WebSockets.Client.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-MT-System.Net.WebSockets.Client.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