Add code coverage support to Arcade SDK with VSTest integration #16206
Build Analysis / Build Analysis
succeeded
Oct 10, 2025 in 0s
.NET Result Analysis
Details
All checks completed
Build Rerun
✔️ Build passed after 1 retries.
(Attempt #1) [link to build]
arcade-pr / Test / Windows_NT / Windows_NT Build_Release / Run Helix Tests
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src\Microsoft.DotNet.Helix\Sdk\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Microsoft.DotNet.Build.Manifest.Tests.dll in job abdad30f-8143-4e95-a3dd-b0e02c4cd8e5 has failed.
[Failure log]
-
❌src\Microsoft.DotNet.Helix\Sdk\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Microsoft.DotNet.Helix.Sdk.Tests.dll in job abdad30f-8143-4e95-a3dd-b0e02c4cd8e5 has failed.
[Failure log]
arcade-pr / Test / Linux / Linux Build_Debug / Run Helix Tests
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/Microsoft.DotNet.Helix/Sdk/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Microsoft.DotNet.Build.Tasks.Workloads.Tests.dll in job 64d01b20-d414-48a7-89e6-5f3ff3bf24bd has failed.
[Failure log]
-
❌src/Microsoft.DotNet.Helix/Sdk/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Microsoft.DotNet.SetupNugetSources.Tests.dll in job 64d01b20-d414-48a7-89e6-5f3ff3bf24bd has failed.
[Failure log]
Non-Deterministic Test Failures Detected
❌ HelixReporter.TRXTests.HelixReporter.TRX.Fail2 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
- AlmaLinux.9.Amd64.Open
- Linux Build_DebugWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_ReleaseWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Linux Build_DebugWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_ReleaseWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- Exception Message
This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.- CallStack
at tests.UnitTest1.TestMethod4() in UnitTest1.cs:line 26
Failing Configurations (12)
❌ HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
- AlmaLinux.9.Amd64.Open
- Linux Build_DebugWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_ReleaseWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Linux Build_DebugWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_ReleaseWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- Exception Message
This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.- CallStack
at tests.UnitTest1.TestMethod1() in UnitTest1.cs:line 13
Failing Configurations (12)
❌ HelixReporterTests.failure1 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
- AlmaLinux.9.Amd64.Open
- Linux Build_DebugWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_ReleaseWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Linux Build_DebugWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_ReleaseWindows.10.Amd64.Open
- Debian.13.Amd64.Open
- Exception Message
Intentional Failure
- CallStack
This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
Failing Configurations (12)
Loading