You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ML.NET CI currently uses the .NET 11 preview SDK but runs its main test jobs on net8.0. Add net10.0 test coverage because .NET 10 is the current LTS release.
Proposed scope
Add net10.0 to the supported test target frameworks.
Install the .NET 10 runtime through the repository tool set.
Make net10.0 the default target for the main CI test jobs.
Keep explicit net8.0 coverage until .NET 8 reaches end of support on November 10, 2026.
Keep the existing .NET Framework 4.8 coverage.
Do not change product target frameworks as part of this issue.
Acceptance criteria
CI builds and runs tests on net10.0 on supported platforms and architectures.
A representative test project passes on net10.0.
Existing net8.0 and net48 compatibility coverage remains available.
I’ve completed the requested .NET 10 CI matrix updates for #7690.
The CI has progressed substantially, with 31 of 38 checks passing. The remaining failures are occurring in existing net8.0/Windows or infrastructure-sensitive test paths, including Windows LocalDB startup, a flaky AutoML recommendation assertion, and a macOS Helix work-item crash. These failures do not indicate that the .NET 10 runtime provisioning or matrix configuration is missing.
Activity
github-actions commentedon Sep 3, 2026
🔍 No similar issues found with high confidence.
AI-powered similar issue detection
Add net10.0 to Helix payload and custom matrices (dotnet#7690)
Update HW intrinsic environment variable switches to DOTNET_ prefix (d…
Use DOTNET_EnableHWIntrinsic in CpuMath unit tests (dotnet#7690)
architdhakar commentedon Sep 27, 2026
I’ve completed the requested .NET 10 CI matrix updates for #7690.
The CI has progressed substantially, with 31 of 38 checks passing. The remaining failures are occurring in existing
net8.0/Windows or infrastructure-sensitive test paths, including Windows LocalDB startup, a flaky AutoML recommendation assertion, and a macOS Helix work-item crash. These failures do not indicate that the .NET 10 runtime provisioning or matrix configuration is missing.@rosebyte Could you please look into this?