-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix detection of unsupported links #58391
Conversation
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsAddresses #57575 (comment).
|
@danmoseley can we backport this to RC2? It was an overlook that should've been fixed in #57996. |
src/libraries/System.IO.FileSystem/tests/Base/SymbolicLinks/BaseSymbolicLinks.FileSystem.cs
Show resolved
Hide resolved
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, modulo my question.
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1183820854 |
src/libraries/System.Private.CoreLib/src/System/IO/FileSystem.Windows.cs
Show resolved
Hide resolved
Obviously this is a good time to see whether you can think of any more missing tests in this area, or other possible similar defects we might have. |
@danmoseley I ran the coverage report ( Opposed to another project (SystemText.Json), where you can see how much source code is being covered: The only difference between both projects is that System.IO code lives in System.Private.CoreLib, I wonder if that's the reason why it doesn't work the same way. EDIT: This is a known issue #51058. |
CI failure seems unrelated (GC tests failed), filed #58409. |
Addresses #57575 (comment).