Handle paths case-insensitively when running tests #4395
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.
Fixes #4393.
@AlexGuteniev discovered that attempting to run tests with a drive letter of a different case would fail (see lowercase
d:
):Later, I discovered that case variation in the middle of the path would also fail (see uppercase
STD
):According to my understanding, this is happening because LLVM's lit machinery isn't performing case normalization before ultimately calling our code, which is performing exact equality checks with
==
. We can fix this on our side by usingos.path.samefile
:This fixes the problematic scenarios, while not affecting what happens if the user specifies a totally nonexistent test.
Click to expand
main
's behavior:Click to expand this PR's behavior: