Make Helix Job Monitor uploads restart-safe - #17179
Build #20260728.19 had test failures
Details
- Failed: 50 (0.99%)
- Passed: 4,610 (91.21%)
- Other: 394 (7.80%)
- Total: 5,054
Annotations
Check failure on line 36 in Build log
azure-pipelines / arcade-pr
Build log #L36
Failed work item information:
Check failure on line 45 in Build log
azure-pipelines / arcade-pr
Build log #L45
Bash exited with code '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
Check failure on line 1 in ExpectedFailureTheoryTest
azure-pipelines / arcade-pr
ExpectedFailureTheoryTest
Test failed