[release/9.0] Use WIF-based Entra auth for OneLocBuild ceapex feed access#17085
Merged
Build Analysis / Build Analysis
succeeded
Jul 14, 2026 in 0s
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
Test Failures (36 tests failed)
🔹 [All failing tests from arcade-pr]
- Exception Message
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.- CallStack
at tests.UnitTest1.TestMethod4() in UnitTest1.cs:line 26
- Exception Message
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.- CallStack
at tests.UnitTest1.TestMethod1() in UnitTest1.cs:line 13
- Exception Message
Intentional Failure
- CallStack
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.- Exception Message
Intentional Failure
- CallStack
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.- Data Driven SubResults
- Exception Message
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.- Stack Trace
at tests.UnitTest2.ExpectedFailureTheoryTest(Int32 i) in UnitTest2.cs:line 16
❌ tests.UnitTest2.ExpectedFailureTheoryTest(i: 3)
- Exception Message
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.- Stack Trace
at tests.UnitTest2.ExpectedFailureTheoryTest(Int32 i) in UnitTest2.cs:line 16
❌ HelixReporter.TRXTests.HelixReporter.TRX.Fail2 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configurations (6)
❌ HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configurations (6)
❌ HelixReporterTests.failure1 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configurations (6)
❌ HelixReporterTests.failure2 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configurations (6)
❌ tests.UnitTest2.ExpectedFailureTheoryTest [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configurations (6)
-
❌ tests.UnitTest2.ExpectedFailureTheoryTest(i: 1)
Was this helpful?
Loading