dupseek: fix test and undeprecate #66509
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was nothing wrong with this tool on Big Sur. The only issue is that the test assumed incorrectly that readdir() would list files in creation-order. This is not true on APFS at least. Therefore when testing if two files are duplicates, either one could be detected as the "dup"
fxcoudert
approved these changes
Dec 8, 2020
|
🤖 A scheduled task has triggered a merge. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was nothing wrong with this tool on Big Sur. The only issue is that the test assumed incorrectly that
readdir()would list files in creation-order. This is not true on APFS at least. Therefore when testing if two files are duplicates, either one could be detected as the "dup"