Dev/mmitche/release10 v4 publishing backport #16696
Build #20260408.10 had test failures
Details
- Failed: 36 (0.39%)
- Passed: 8,678 (94.92%)
- Other: 428 (4.68%)
- Total: 9,142
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.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