[release/8.0] Switch to non-preview 2022 queue#65413
Merged
Merged
Build Analysis / Build Analysis
failed
Feb 13, 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.
Known Infrastructure Errors
-
❌20260212.24 / Build / Build: macOS arm64 / Checkout dotnet/aspnetcore@refs/pull/65413/merge to s and 4 more hits - Unable to checkout
-
❌20260212.24 / Build / Build: macOS arm64 / Checkout dotnet/aspnetcore@refs/pull/65413/merge to s and 4 more hits - Checkout failure: "Git fetch failed with exit code 128"
-
❌20260212.15 / Test: Blazor E2E tests on Linux / Checkout dotnet/aspnetcore@refs/pull/65413/merge to s - Unable to checkout
-
❌20260212.15 / Test: Blazor E2E tests on Linux / Checkout dotnet/aspnetcore@refs/pull/65413/merge to s - Checkout failure: "Git fetch failed with exit code 128"
Build Failures
aspnetcore-ci / Build / Build: macOS arm64 / Upload cores
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌Bash exited with code '127'.
aspnetcore-ci / Build / Build: macOS x64 / Upload cores
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌Bash exited with code '127'.
aspnetcore-ci / Build / Build: Linux ARM / Upload cores
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌Bash exited with code '127'.
4 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [aspnetcore-ci] [aspnetcore-components-e2e] [aspnetcore-quarantined-pr]
Was this helpful?
Loading