-
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
DriveInfo tests fail if current user uses SUBST #14027
Comments
@Priya91, can you take a look? |
@terrajobst yes, working on this. |
According to MSDN, a SUBST.EXE created mapping should NOT be considered a valid mapped drive. We follow the same in our project, https://github.com/alphaleonis/AlphaFS |
Disable running tests for this project as many of them are failing randomly for different reasons, including but not limited to requiring admin to set/reset drive labels, doing exact total disk space comparisions while other disk IO on the system may be changing it actively, and failing on subst drives, etc There are various github issues covering some of these see: https://github.com/dotnet/corefx/issues/514 https://github.com/dotnet/corefx/issues/528 https://github.com/dotnet/corefx/issues/549 https://github.com/dotnet/corefx/issues/564 https://github.com/dotnet/corefx/issues/592
Triage: Rare case, but disabled test. We should fix. |
As mentioned above https://github.com/dotnet/corefx/issues/549#issuecomment-72322352 this type of drive shouldn't be considered. Need to look deeper at expected behavior in this case and update tests to either skip in this case or handle appropriately. |
On my machine I'm using SUBST to map folders as drives. This causes the the drive info tests to fail:
I would expect the drive info tests to be resilient to this.
The text was updated successfully, but these errors were encountered: