Fix WindowsFS test failure seen on Policeman Jenkins #14706
Merged
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.
This fixes the following failure seen on Polceman Jenkins:
I added code to print the filename when test fails. What happens here. The test generates the following filename:
m:NfDcLQOn Linux this correctly fails the test because the filename triggers our code. But on real WIndows, the resolve call does not fail the test, because "m:" is treated as a drive letter and then it resolves. Our code then does not get triggered, because the filename itsself is not starting with
m:, it is onlyNfDcLQ(on drive M's CWD).The same happens when the filename starts with a real slash/backslash. To work asound both cases, trhe file name should have at least 2 random characters before the invalid character.
xy:is not treated as drive letter and fails correctly also on Windows.