Handle createLink post security manager in StoreRecoveryTests #129964
+1
−10
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.
When running under security manager an assumption was made that failing to create a hard link due to security exception implied hard links were supported. Now that security manager is gone, the code to create a hard link in StoreRecoveryTests executes. But in the case of windows, BasicFileAttributes.fileKey does not return a unique object that can be used to verify a link exists. Yet the fact createLink returned is enough to trust the jdk was able to create a link.
closes #124104