Skip to content

Add xLocCustomPowerShellScript in OneLoc task

bb17d3d
Select commit
Loading
Failed to load commit list.
Merged

Add xLocCustomPowerShellScript in OneLoc task #16693

Add xLocCustomPowerShellScript in OneLoc task
bb17d3d
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Apr 8, 2026 in 1h 17m 34s

Build #20260407.8 had test failures

Details

Tests

  • Failed: 48 (0.38%)
  • Passed: 12,174 (96.47%)
  • Other: 398 (3.15%)
  • Total: 12,620

Annotations

Check failure on line 1 in HelixReporter.TRXTests.Fail1

See this annotation in the file changed.

@azure-pipelines 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

Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRX.Fail2

See this annotation in the file changed.

@azure-pipelines 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

Check failure on line 1 in tests.UnitTest2.ExpectedFailureTheoryTest

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

tests.UnitTest2.ExpectedFailureTheoryTest

Test failed

Check failure on line 1 in HelixReporterTests.failure1

See this annotation in the file changed.

@azure-pipelines 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.