Bump Microsoft.Build from 17.12.50 to 18.6.3#16886
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Build Analysis / Build Analysis
failed
May 25, 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.
Build Failures
arcade-pr / Test / Monitor Helix Jobs / Monitor Helix Jobs
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]-
❌Bash exited with code '1'.
Test Failures (896 tests failed)
🔹 [All failing tests from arcade-pr]
- Linux Build_Debug run on OSX.15.Amd64.Open [HelixJob:7ccd5787-7487-4624-bfaf-374c48621dc4]
- Windows_NT Build_Release run on OSX.15.Amd64.Open [HelixJob:cc9dfe18-be42-4152-b0d1-9a509f1ed5a9]
- Linux Build_Debug run on Windows.11.Amd64.Client.Open [HelixJob:2f98f042-d3f8-4718-8123-a18a1b0be07c]
- AlmaLinux.9.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open [HelixJob:8fd97762-a3f6-4a95-97c6-25ca08ebbb0c]
- 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
❌ 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
- Linux Build_Debug run on OSX.15.Amd64.Open [HelixJob:7ccd5787-7487-4624-bfaf-374c48621dc4]
- Windows_NT Build_Release run on OSX.15.Amd64.Open [HelixJob:cc9dfe18-be42-4152-b0d1-9a509f1ed5a9]
- Linux Build_Debug run on Windows.11.Amd64.Client.Open [HelixJob:2f98f042-d3f8-4718-8123-a18a1b0be07c]
- AlmaLinux.9.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open [HelixJob:8fd97762-a3f6-4a95-97c6-25ca08ebbb0c]
- 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
- Linux Build_Debug run on OSX.15.Amd64.Open [HelixJob:7ccd5787-7487-4624-bfaf-374c48621dc4]
- Windows_NT Build_Release run on OSX.15.Amd64.Open [HelixJob:cc9dfe18-be42-4152-b0d1-9a509f1ed5a9]
- Linux Build_Debug run on Windows.11.Amd64.Client.Open [HelixJob:2f98f042-d3f8-4718-8123-a18a1b0be07c]
- AlmaLinux.9.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open [HelixJob:8fd97762-a3f6-4a95-97c6-25ca08ebbb0c]
- 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
- Linux Build_Debug run on OSX.15.Amd64.Open [HelixJob:7ccd5787-7487-4624-bfaf-374c48621dc4]
- Windows_NT Build_Release run on OSX.15.Amd64.Open [HelixJob:cc9dfe18-be42-4152-b0d1-9a509f1ed5a9]
- Linux Build_Debug run on Windows.11.Amd64.Client.Open [HelixJob:2f98f042-d3f8-4718-8123-a18a1b0be07c]
- AlmaLinux.9.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open [HelixJob:8fd97762-a3f6-4a95-97c6-25ca08ebbb0c]
- 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.
- Linux Build_Debug run on OSX.15.Amd64.Open [HelixJob:7ccd5787-7487-4624-bfaf-374c48621dc4]
- Windows_NT Build_Release run on OSX.15.Amd64.Open [HelixJob:cc9dfe18-be42-4152-b0d1-9a509f1ed5a9]
- Linux Build_Debug run on Windows.11.Amd64.Client.Open [HelixJob:2f98f042-d3f8-4718-8123-a18a1b0be07c]
- AlmaLinux.9.Amd64.Open
- AlmaLinux.9.Amd64.Open
- Windows_NT Build_Release run on Windows.11.Amd64.Client.Open [HelixJob:8fd97762-a3f6-4a95-97c6-25ca08ebbb0c]
- 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.
❌ ExpectedFailureTheoryTest [Console] [Details] [Artifacts] [100.00% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configurations (6)
-
❌ ExpectedFailureTheoryTest(i: 1)
❌ 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.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)
Was this helpful?
Loading