[👶 PR] Improve Launcher to handle SLURM_TMPDIR #228
Merged
Conversation
This file contains 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
vict0rsch
changed the title
|
The 👶 is becoming a 👦 ? |
carriepl
approved these changes
Oct 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
launch.pynow handlescode_dir: $SLURM_TMPDIRor--code_dir='$SLURM_TMPDIR'If this is used, the sbatch script will:
1.
git clonethe repo2.
git checkoutwhatever value is ingit_checkout:or--git_checkout=. Ifgit_checkoutis empty, the current branch name is used💥 Warning: from the command-line, single quotes are mandatory around
'$SLURM_TMPDIR'otherwise bash will try to evaluate it instead of giving the raw string to Python(From #224)