-
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
Re-enable long path test to get exception message [NO MERGE] #64079
Conversation
…wsException (dotnet#64044)" This reverts commit a7aff06.
Tagging subscribers to this area: @dotnet/area-system-io |
/azp help |
Supported commands
See additional documentation. |
/azp list |
Odd it didn't fail the first time. But we got this:
@JeremyKuhne do you know what setting might cause I don't think it has anything to do with long path settings |
If not, I'm inclined to call this wierd emergent Windows behavior and adjust the test to allow IOException when on Windows 11 and call it good. |
That is what I would do. It isn't documented what exception you get exactly when you overflow what will fit in a Windows Unicode string. I don't think it will materially impact .NET users. This test is more for tracking Windows behavior changes, so we can go back and see what changed and when should it come up in some report/scenario. |
This reverts commit a7aff06.
Get the string provided by the logging added in e2da32c
Not to be merged.
cc @MattGal