fix: Fix broken test and update .Tests to .net 9.0 #76
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.
Problem
The CI/CD pipeline was failing on both Ubuntu and macOS with critical test execution errors:
The active test run was aborted. Reason: Test host process crashed : No usable version of libssl was foundCould not find 'dotnet' host for the 'X64' architectureThese failures resulted in 0 tests running across all platforms, making the build pipeline completely non-functional.
Root Cause
The test project was targeting
netcoreapp3.1, which is deprecated and end-of-life. This framework has known compatibility issues with:Solution
Upgraded the test project target framework from
netcoreapp3.1tonet6.0LTS and removed the unnecessaryOutputType=Exeproperty:Impact
The main library continues to target
netstandard2.0for broad compatibility, while the test project now uses a modern, supported framework. This minimal change resolves the infrastructure issues without affecting the library's public API or functionality.The one remaining test failure (
ExecuteProcess_PingLocalhost_Success) is a pre-existing platform-specific issue unrelated to the framework upgrade, where the ping command output format differs from expectations.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.