[lldb] fix tests with spaces in command path #138714
Open
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.
Summary
LLDB tests will fail with the "command not found" error if there are spaces in the command path.
This PR fixes the issue by quoting the command.
Description
The path of a command that was substituted in a test file (for instance
lld-link
) may contain spaces. On windows, it will start willC:\Program Files\...
. This will cause the command to be parsed as['C:\Program', 'Files\...', ...
.This causes the tests to fail.
Fix
During the parsing stage of the test file, we use
shlex.quote
to shell escape the command path. The command is test parsed correctly byShUtil.ShParser.parse
and the rest of the flow is executed as expected.