Add BotAccount-dotnet-maestro-bot-mirroring-PAT for mirror pipelines - #17088
Merged
Azure Pipelines / arcade-pr
succeeded
Jul 9, 2026 in 1h 4m 5s
Build #20260709.3 had test failures
Details
- Failed: 48 (1.09%)
- Passed: 3,966 (89.97%)
- Other: 394 (8.94%)
- Total: 4,408
Annotations
Check failure on line 1 in XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath
azure-pipelines / arcade-pr
XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath
Intentional Failure 🍕 \r \n \t \a \b \v \f \0\r\nExpected: True\r\nActual: 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
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
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.TRX.Fail2
azure-pipelines / arcade-pr
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
Loading