Closed
Conversation
This appears to cause the execution to hang, or something.
Member
Author
|
Might be more correct to replace |
Member
Author
|
The exec was not at fault. See #6582. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It seems like the change in #6226 (backported as #6568) to use
execto run the subcommand after doing anshtochdirmay be causingsystemwithchdirto hang under some circumstances (#6579).This PR removes the exec, which should put us back to the old behavior other than how we handle the actual command args by evaluating
"$@".cc @mrnoname1000 for assistance