-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Also build for net8.0 #332
Conversation
Test Results 4 files + 2 404 suites +202 2h 45m 10s ⏱️ + 1h 22m 15s Results for commit 8fe98b5. ± Comparison against base commit 04eda79. This pull request skips 1 test.
♻️ This comment has been updated with latest results. |
v2.1.0 was still trying to build against win7-x32 runtimes, which are no longer offered in .NET 8. If we're using recent .NET, we need a recent setup-dotnet version.
The tests take two hours to run now that we have net461, net6.0, and net8.0 target frameworks. They're all passing except for one that's known to be flaky and timing-dependant, so it's safe to disable them while we work on fixing the part of the build that comes after the tests. Then once that's working we'll revert this commit.
This reverts commit 376030a.
The GitHub Actions runners are apparently slow to deliver filesystem notifications, which is exactly the scenario that makes this test useless. It's already disabled on Windows; there's no reason for it to cause the CI build to fail all the time when it's the only failing test.
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.
LGTM, except one thing that is more on the nitpick side...
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.
LfMerge wants to move to run on net8.0 rather than net6.0; this will require a chorusmerge build that can run on net8.0.
This change is