[release/10.0] Enable microbuild preview plugin (backport of #16185)#16821
[release/10.0] Enable microbuild preview plugin (backport of #16185)#16821davidfowl wants to merge 2 commits into
Build #20260514.33 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 32 in Build log
azure-pipelines / arcade-pr
Build log #L32
Artifact Logs_Test_Linux_Debug_Helix already exists for build 1421682.
Check failure on line 32 in Build log
azure-pipelines / arcade-pr
Build log #L32
Artifact Logs_Test_Windows_NT_Release_Helix already exists for build 1421682.
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.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
Check failure on line 1 in tests.UnitTest2.ExpectedFailureTheoryTest
azure-pipelines / arcade-pr
tests.UnitTest2.ExpectedFailureTheoryTest
Test failed