[release/10.0] Remove audit sources from NuGet.config#16357
Merged
Azure Pipelines / arcade-pr
succeeded
Nov 26, 2025 in 1h 18m 51s
Build #20251126.1 had test failures
Details
- Failed: 36 (0.39%)
- Passed: 8,660 (94.91%)
- Other: 428 (4.69%)
- Total: 9,124
Annotations
Check failure on line 1 in HelixReporterTests.failure1
azure-pipelines / arcade-pr
HelixReporterTests.failure1
Intentional Failure
Raw output
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.
Check failure on line 1 in HelixReporterTests.failure2
azure-pipelines / arcade-pr
HelixReporterTests.failure2
Intentional Failure
Raw output
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.
Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRX.Fail2
azure-pipelines / arcade-pr
HelixReporter.TRXTests.HelixReporter.TRX.Fail2
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.
Raw output
at tests.UnitTest1.TestMethod4() in UnitTest1.cs:line 26
Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1
azure-pipelines / arcade-pr
HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1
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.
Raw output
at tests.UnitTest1.TestMethod1() in UnitTest1.cs:line 13
Loading