Migrate test infrastructure from xUnit v2 to xUnit v3#52930
Merged
Build Analysis / Build Analysis
failed
Mar 10, 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
Build Failures
dotnet-sdk-public-ci / Build / TestBuild: linux (x64)
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The job running on agent NetCore-Public 369 ran longer than the maximum time of 150 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
Test Failures (3 tests failed)
🔹 [All failing tests from dotnet-sdk-public-ci]
❌ Microsoft.CodeAnalysis.NetAnalyzers.UnitTests.dll.129.WorkItemExecution [Console] [Details] [Artifacts] [1.40% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
❌ Microsoft.CodeAnalysis.NetAnalyzers.UnitTests.dll.130.WorkItemExecution [Console] [Details] [Artifacts] [2.55% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
❌ Microsoft.CodeAnalysis.NetAnalyzers.UnitTests.dll.37.WorkItemExecution [Console] [Details] [Artifacts] [1.40% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
Was this helpful?
Loading