Remove roslyn pr-tagger PATs from dnceng-partners-kv manifest #16702
+0
−22
Azure Pipelines / arcade-pr
succeeded
Apr 23, 2026 in 41m 30s
Build #20260423.14 had test failures
Details
- Failed: 48 (1.26%)
- Passed: 3,358 (88.28%)
- Other: 398 (10.46%)
- Total: 3,804
Annotations
Check failure on line 1 in XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath
azure-pipelines / arcade-pr
XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath
Intentional Failure 🍕
Expected: True
Actual: False
Raw output
at XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath() in Class1.cs:line 1
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.Fail1
azure-pipelines / arcade-pr
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