Repository navigation
build: move main to the .NET 11 GA SDK and Npgsql's provider rc.3, and let the core tests end on it - #536
Merged
Conversation
… is a test argument (#535) A DynamicData row's arguments travel in every message the test host sends about the row. With the hostile text as an argument, one results message of ParserResilienceTests was 20 MB, and vstest.console in SDK 11.0.100 ran at full CPU on it for ten minutes without ending the run. The same assembly passed in 8 seconds through SDK 11.0.100-rc.2's runner. The rows now hold the name, and each test builds its text from it. The largest message in a --diag log is 31 KB, and the suite ends in 3 seconds on SDK 11.0.100. Found-By: CA Defect-Class: PKG Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…Npgsql's provider rc.3 (#532) - global.json names SDK 11.0.100, and release.yml no longer asks setup-dotnet for a preview build. - Npgsql.EntityFrameworkCore.PostgreSQL and its NodaTime plugin move to 11.0.0-rc.3, and Microsoft.EntityFrameworkCore.Design with them: rc.3 pins EF Core to exactly rc.3, so EF Core 11.0.0 waits for Npgsql (#533). - The test packages that don't depend on EF Core move to 11.0.0 (ASP.NET Core OpenApi and TestHost, Microsoft.Extensions.Configuration and its Binder), and MSTest to 4.5.2. - The changelogs and docs/efcore.md name rc.3. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ill in .NET 11.0.0 (#532) The minimal repro from the upstream issue, published with Native AOT on SDK 11.0.100, ends with SIGTRAP (exit 133) when the default IFormattable.ToString may be inlined, and prints its two lines with NoInlining. The fix's backport to release/11.0 (dotnet/runtime#136148) is approved for servicing and not merged, so the NoInlining attribute and the per-family overrides stay. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
CaffeinatedCoder
added
chore
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #532
Closes #535
Problem
.NET 11 has been generally available since 2026-11-10, and
mainwas still on the RC2 toolchain:global.jsonpinned SDK11.0.100-rc.2, the test packages were at rc.2, and no measurement of the retarget had been repeated on the GA runtime.Moving to the GA SDK showed a second problem.
dotnet testover the core test project did not end on SDK 11.0.100: every test passed, thenvstest.consoleran at full CPU for ten minutes (#535).global.jsonsaysrollForward: latestFeature, so any machine or CI job that installs the newest 11.0.1xx SDK had this runner already.Change
global.jsonnames SDK11.0.100.release.ymlno longer askssetup-dotnetfor a preview build.Npgsql.EntityFrameworkCore.PostgreSQL, its NodaTime plugin andMicrosoft.EntityFrameworkCore.Designmove to rc.3, in one change. rc.3 pins EF Core to exactly rc.3, so EF Core 11.0.0 waits for Npgsql (main: move the EF Core and Npgsql floors to 11.0.0 when Npgsql's provider ships it #533).ParserResilienceTests: theDynamicDatarows carry only the name, and each test builds its hostile text from it. With the text as an argument, one results message was 20 MB.docs/efcore.mdname rc.3. The comment on the Native AOT workaround inIValueSetFactory.csrecords the GA measurement.Tests
Measured on macOS arm64; the full record is in this comment on #532.
test/consumer-smoke-test.shwith the Native AOT consumer (99ok, noFAIL).--diaglog is 31 KB.ToStringtraps (SIGTRAP) in the defaultIFormattable.ToStringofIValueSetFactory<TSet, T>#291 is still in .NET 11.0.0 (exit 133 for the upstream repro, clean withNoInlining), so the workaround stays.closedcompiles as stable C# 15 on the GA compiler, fornet10.0andnet11.0.Not done here: a reproduction of #535 for microsoft/vstest, and the cherry-pick of the test change to
release/10.x, which #534 needs before that branch builds with SDK 11.🤖 Generated with Claude Code