Use Entra credential for symbol upload, removing dnceng-symbol-server-pat #16688
Build Analysis / Build Analysis
succeeded
Apr 27, 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 (48 tests failed)
🔹 [All failing tests from arcade-pr]
- Windows_NT Build_Release run on AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open
- Windows_NT Build_Release run on Debian.13.Amd64.Open
- Windows_NT Build_Release run on OSX.15.Amd64.Open
- Linux Build_Debug run on AlmaLinux.9.Amd64.Open
- Linux Build_Debug run on Windows.11.Amd64.Client.Open
- Linux Build_Debug run on Debian.13.Amd64.Open
- Linux Build_Debug run on OSX.15.Amd64.Open
- 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
- Windows_NT Build_Release run on AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open
- Windows_NT Build_Release run on Debian.13.Amd64.Open
- Windows_NT Build_Release run on OSX.15.Amd64.Open
- Linux Build_Debug run on AlmaLinux.9.Amd64.Open
- Linux Build_Debug run on Windows.11.Amd64.Client.Open
- Linux Build_Debug run on Debian.13.Amd64.Open
- Linux Build_Debug run on OSX.15.Amd64.Open
- 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
- Windows_NT Build_Release run on AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open
- Windows_NT Build_Release run on Debian.13.Amd64.Open
- Windows_NT Build_Release run on OSX.15.Amd64.Open
- Linux Build_Debug run on AlmaLinux.9.Amd64.Open
- Linux Build_Debug run on Windows.11.Amd64.Client.Open
- Linux Build_Debug run on Debian.13.Amd64.Open
- Linux Build_Debug run on OSX.15.Amd64.Open
- 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.- Windows_NT Build_Release run on AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open
- Windows_NT Build_Release run on Debian.13.Amd64.Open
- Windows_NT Build_Release run on OSX.15.Amd64.Open
- Linux Build_Debug run on AlmaLinux.9.Amd64.Open
- Linux Build_Debug run on Windows.11.Amd64.Client.Open
- Linux Build_Debug run on Debian.13.Amd64.Open
- Linux Build_Debug run on OSX.15.Amd64.Open
- 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.- Windows_NT Build_Release run on AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open
- Windows_NT Build_Release run on Debian.13.Amd64.Open
- Windows_NT Build_Release run on OSX.15.Amd64.Open
- Linux Build_Debug run on AlmaLinux.9.Amd64.Open
- Linux Build_Debug run on Windows.11.Amd64.Client.Open
- Linux Build_Debug run on Debian.13.Amd64.Open
- Linux Build_Debug run on OSX.15.Amd64.Open
- 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.Fail1 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (8)
❌ HelixReporter.TRXTests.HelixReporter.TRX.Fail2 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (8)
❌ HelixReporterTests.failure1 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (8)
❌ HelixReporterTests.failure2 [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (8)
❌ tests.UnitTest2.ExpectedFailureTheoryTest [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (8)
-
❌ tests.UnitTest2.ExpectedFailureTheoryTest(i: 1)
Was this helpful?
Loading