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.
It seems that GitHub Actions' Linux runner has been updated with new versions of
libssl
andlibicu
(perhaps inherited from a new version of Ubuntu). However, .NET 2.1 and 3.1 are hard-coded to only support specific versions of those libraries. Long story short, after about 4 hours of work, I finally got the CI tests running again. In general:Almost everything still gets tested on Windows and passes as before. It's just Linux that is having an issue. The Azure Function sample project is demonstrating the in-process configuration model. This model only runs on .NET 6 under Windows and will go out of support late 2026. Perhaps sometime we can update or add a sample for the out-of-process configuration model which supports .NET 8 and is the currently-recommended integration path for Azure Functions. Either way I believe Azure Functions always run under Windows, and so the fact that it cannot be tested on Linux is irrelevant.
As a reminder, ASP.NET Core 2.1 is still fully supported by MS on Windows when run under supported versions of the .NET Framework. I use this configuration for one of my projects. As such, I think it important to retain testing for ASP.NET Core 2.1 on the .NET Framework under Windows.
I'm fine if we need to drop testing for unsupported STS releases such as .NET 5.0 or old unsupported LTS releases such as .NET 3.1. However, to the degree that it is easy enough to configure the test runner to test these platforms, especially platforms that have recently fallen out of support, I feel there is no reason not to do so. As such, I've configured testing on as many of these platforms as will still run correctly.
The solution does provide a way to configure local testing to only use a single platform - configure the
SingleTestPlatform
msbuild property totrue
. Or just run the specific tests you require.