.NET 7.0 support - #4224
Conversation
Mostly based on nunit@6cbe01e
| <group targetFramework="net6.0"> | ||
| <dependency id="NUnit" version="[$version$]" /> | ||
| </group> | ||
| <group targetFramework="net7.0"> |
There was a problem hiding this comment.
@manfred-brands Wondering if I can ask your confirmation of my understanding here since you did the previous upgrades in this area. This would apply to the framework of the consuming app I think, right?
There was a problem hiding this comment.
@stevenaw If the app consuming nunitlite targets any of the listed framework, it will automatically add a transient dependency on the packages listed here.
|
Thanks for your hard work on working through some of the issues on this @KonH . As you mention, this won't be able to be merged until after Hacktoberfestt is complete so I've added the |
| #if NET7_0_OR_GREATER | ||
| [TestCase(nameof(WarningFixture.WarningInThreadPoolQueueUserWorkItem), 4, ExcludePlatform = "MacOSX")] | ||
| [TestCase(nameof(WarningFixture.WarningInThreadPoolQueueUserWorkItem), 5, IncludePlatform = "MacOSX")] | ||
| #else |
There was a problem hiding this comment.
Is this because of "InvokeStub_" lines not removed here?
There was a problem hiding this comment.
Not exactly, I described it here - #4170 (comment)
manfred-brands
left a comment
There was a problem hiding this comment.
Some small suggestions, otherwise it looks good to me.
|
.NET 7 was released, and final changes applied |
|
The latest fail looks flaky, the previous run completed successfully and changes between them are not related. |
|
Thanks @KonH I've pulled the changes and they run + pass fine locally for me. @nunit/framework-team This failing test was also a confusing issue for contributors during Hacktoberfest. Are there any objections to @KonH temporarily bumping up this value until it can be investigated? Perhaps just the one |
|
@stevenaw I have increased timeout, now tests passed |
* Initial changes to support .NET 7 RC - #4170 Mostly based on 6cbe01e * NuGet packaging changes to support .NET 7 RC - #4170 Based on 6cbe01e * Continuous integration changes to support .NET 7 RC - #4170 Based on 6cbe01e * Try to fix .NET 7.0 lookup on Azure Pipelines - #4170 * It looks like we need both .NET 6.0 and .NET 7.0 to run tests on Azure Pipelines - #4170 * Use valid version for .NET 6.0 on Azure Pipelines - #4170 * Use different test settings for .NET 7 to cover corner-case - #4170 * Add potential workaround for flaky test behaviour on .NET 7 - #4170 * On MacOS test behaviour is different on .NET 7 - #4170 * Change setup-dotnet action version (for new lines only) #4224 (comment) * Use release version of .NET 7.0 * Refactor: do not copy collections, use single method * Temporary increase test timeout * Temporary increase test timeout #2
* Initial changes to support .NET 7 RC - #4170 Mostly based on 6cbe01e * NuGet packaging changes to support .NET 7 RC - #4170 Based on 6cbe01e * Continuous integration changes to support .NET 7 RC - #4170 Based on 6cbe01e * Try to fix .NET 7.0 lookup on Azure Pipelines - #4170 * It looks like we need both .NET 6.0 and .NET 7.0 to run tests on Azure Pipelines - #4170 * Use valid version for .NET 6.0 on Azure Pipelines - #4170 * Use different test settings for .NET 7 to cover corner-case - #4170 * Add potential workaround for flaky test behaviour on .NET 7 - #4170 * On MacOS test behaviour is different on .NET 7 - #4170 * Change setup-dotnet action version (for new lines only) #4224 (comment) * Use release version of .NET 7.0 * Refactor: do not copy collections, use single method * Temporary increase test timeout * Temporary increase test timeout #2
Changes required to support .NET 7.0
Work in progress, .NET 7.0 RC should be changed when a stable version is released
Related (and more details provided) to #4170