-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to .NET SDK 7.0 Preview 2 #27447
Conversation
@dotnet/efteam Should we update our tests (and benchmarks) to run on net7.0 or wait? |
Looks like there are a few failures in the analyzers tests.
|
test/EFCore.Analyzers.Tests/UninitializedDbSetDiagnosticSuppressorTest.cs
Outdated
Show resolved
Hide resolved
Hmm, looks like there's some failure around Trimming now... |
Huh? Tried to fix the trimming by running the resulting executable from the right directory (net7.0 instead of net6.0), now there's a new test failure on AddressAndPayment_RedirectToCompleteWhenSuccessful |
@maumar, do you want to dig into the MusicStoreInMemoryTest.AddressAndPayment_RedirectToCompleteWhenSuccessful failure?
|
And now there's a new exception being thrown from System.Text.Json.
|
@Pilchie Is the Json exception a known issue? |
Not known to me. @danmoseley - any ideas? |
@dotnet/aspnet-build - any of you seen this in .NET 7 builds? |
Looks like you might be building one version of the runtime while running against another - there may be other |
@wtgodbe We still want to target .NET 6 with our product assemblies, but we want our tests to use .NET 7. (Ideally, we won't target .NET 7 even when we ship RTM since that forces people off an LTS framework, which many people don't want to do.) |
Just saw dotnet/aspnetcore#40471 from @jkotas which looks like it might be related? |
Yes, it is related, but I do not think it is the root cause of the build break. The change that removed S.R.CS.Unsafe package in dotnet/runtime is not included in .NET 7 preview1. If you see build breaks due to do this package removal, you are mixing .NET 7 preview1 bits with some newer bits. It is not unusual to see intra-release breaking changes in previews like this one. Mixing bits from different previews will expose you to the intra-release breaking changes like that. |
Thanks! We typically only hit a few of these breaks each release. We find that saying on released previews of the SDK and runtime helps contributors immensely since they don't have to worry about setting environment variables before launching their IDE. I'll pin a few packages to their Preview 1 versions for now. If this continues to be a problem, we can consider flowing the runtime again (at the expense of productivity and contributors). |
@maumar Looks like SQL Server and SQLite are now failing with the same error. |
@bricelam AddressAndPayment_RedirectToCompleteWhenSuccessful also happens due to
|
|
Hello @bricelam! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:
These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check. Give feedback on thisFrom the bot dev teamWe've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments. Please reach out to us at fabricbotservices@microsoft.com to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin. |
New failures in EFCore.OData.FunctionalTests after updating to Preview 2. |
|
Yep. That's the one. @maumar Would it be possible (without a ton of infrastructure) to show the server-side errors on failure? |
@bricelam OData tests fail due to:
|
789d401
to
2696b36
Compare
<MicrosoftExtensionsConfigurationAbstractionsVersion>7.0.0-preview.3.22171.1</MicrosoftExtensionsConfigurationAbstractionsVersion> | ||
<MicrosoftExtensionsConfigurationEnvironmentVariablesVersion>7.0.0-preview.3.22171.1</MicrosoftExtensionsConfigurationEnvironmentVariablesVersion> | ||
<MicrosoftExtensionsConfigurationJsonVersion>7.0.0-preview.3.22171.1</MicrosoftExtensionsConfigurationJsonVersion> | ||
<SystemCollectionsImmutableVersion>7.0.0-preview.2.22152.2</SystemCollectionsImmutableVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this change we have downgraded our dependencies in main branch. Is that required? Do we need to get main to upgrade dependencies again?
cc: @dotnet/aspnet-build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will unpin once we upgrade to Preview 3 of the SDK (see conversation above)
Still waiting for the official release, so the version number may change again before I merge, but this one is close.