More fixes for scripts run.command() in 0.3.16 #922
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.
Following on from discussion in #920.
I thought that perhaps there was some sort of network file system race condition that was causing the annoying
standard_space_roimissing file issue in5ttgen fsl(hence functionfile.waitFor()). It now appears as though it'sshnot finding the script, yet giving a 0 return code. Differences insubprocessbetween Python versions may have contributed to the prior confusion in diagnosing - on top of thesherror message not being found until the-debugoption was used.Independently of the
standard_space_roiissue, this function can also be used to wait for therun_first_alloutput rather than globally disabling SGE.Need to confirm that this still works on Windows.