fix: skip extended-length and invalid path tests on .NET Framework#1051
Merged
vbreuss merged 1 commit intoJul 11, 2026
Merged
Conversation
On .NET Framework 'Path.GetFullPath' rejects '\?\' device paths and throws a culture-dependent exception for invalid paths, so these tests fail unreliably (they turn red once tests are forced to run under the invariant culture). Skip them on .NET Framework; they continue to run and pass on modern targets.
|
|
This is addressed in release v7.0.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
On .NET Framework 'Path.GetFullPath' rejects '?' device paths and throws a culture-dependent exception for invalid paths, so these tests fail unreliably (they turn red once tests are forced to run under the invariant culture). Skip them on .NET Framework; they continue to run and pass on modern targets.