-
Notifications
You must be signed in to change notification settings - Fork 209
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
Allow FileInfo_Query_FileIdInformation tests on OTHERFS #256
base: main
Are you sure you want to change the base?
Conversation
The test function FileInfo_Query_FileIdInformation tries to use FSCTL_READ_FILE_USN_DATA on OTHERFS, which is generally not going to work. I've modified this function to only try that on NTFS or REFS.
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
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.
We checked the file system at beginning of FileInfo_Query_FileIdInformation, so could you update your PR as below:
Modify line 40
BaseTestSite.Assume.AreNotEqual(FileSystem.FAT32, fsaAdapter.FileSystem, "File system should not be FAT32.");
something like below:
If(!(this.fsaAdapter.FileSystem == FileSystem.NTFS || this.fsaAdapter.FileSystem == FileSystem.REFS))
{
site.Assume.Inconclusive("FileInfo_Query_FileIdInformation only supported by NTFS or REFS file system.");
}
Reporting "Inconclusive" for other than NTFS or REFS seems OK. I'd prefer that we could test the FileIdInformation info. level on OTHERFS |
That sounds reasonable, how about updating the changes as below:
This will provide a way for OTHERFS if it supports FileIdInformation(by update following change) and wants to test.
|
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
The test function FileInfo_Query_FileIdInformation
tries to use FSCTL_READ_FILE_USN_DATA on OTHERFS,
which is generally not going to work.
I've modified this function to only try that on
NTFS or REFS.
This could be a possible fix for microsoft/ProtocolTestFramework#35