-
-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Scheduling jobs" -- remark about environment variables is incorrect #48
Comments
Can you pinpoint me to the specific position in the episode, please? |
It's towards the end of the episode. In the "Other types of jobs" sub-heading, there's a paragraph that begins "srun takes the same options as sbatch" -- the parenthetical remark at the end of that paragraph is the wording I'm referring to. |
I just ran a few more tests, and even in the case where "bash" is not run (e.g. the "echo" example in the lesson), the SLURM environment variables appear to be set. |
Reworded the text about SLURM environment variables. Fixes issue #48.
In the "Scheduling jobs" episode, under the "other types of jobs" subsection, there is a remark that environment variables are not available for interactive jobs launched via "srun". On the two SLURM clusters available to me, this is not true for either of them -- doing "srun" followed by "env" shows that in the shell session, the "SLURM_*" environment variables are set, and the explicitly-mentioned SLURM_CPUS_PER_TASK variable is set if the "-c" flag was provided to "srun".
This might be configurable, and vary from one installation to another?
The text was updated successfully, but these errors were encountered: