-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Unix throws the wrong exception creating a FileStream #21801
Comments
There is a PR to fix the behavior in FileStream in CoreCLR. This test will pass as per the Windows OS block once that change is taken. Disabling and tracking to allow taking a new drop.
There is a PR to fix the behavior in FileStream in CoreCLR. This test will pass as per the Windows OS block once that change is taken. Disabling and tracking to allow taking a new drop.
There is a PR to fix the behavior in FileStream in CoreCLR. This test will pass as per the Windows OS block once that change is taken. Disabling and tracking to allow taking a new drop.
There is a PR to fix the behavior in FileStream in CoreCLR. This test will pass as per the Windows OS block once that change is taken. Disabling and tracking to allow taking a new drop.
Corelib is updated, need to remove the skips when we take the next drop. |
Reopening to track port to rel/2.0.0 branch. |
@karelz, the actual fix is already in the rel/2.0 branch, no? The only thing I did and that closed this was re-enabling tests in master. You're reopening this to track re-enabling those tests in 2.0 as well? |
I don't see any PR in this issue against rel/2.0.0 branch. If there is one, let's link them properly. |
I let you as experts decide if we need to re-enable the tests in rel/2.0.0 branch. If there is value, I'd suggest to do it. |
I'll open a separate issue for porting the test. dotnet/coreclr#11757 fixed this in CoreCLR for master. |
Same underlying issue as #21745. Need to update CoreLib to throw DirectoryNotFound if the directory doesn't exist. (
/directory/doesnotexist/doesnotexist
)The text was updated successfully, but these errors were encountered: