We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the file https://github.com/FZJ-JSC/JUBE/blob/29aaf678069551dc6f26a775ee831852bef7d11f/platform/slurm/chainJobs.sh
The job ids are extracted after submitting to slurm. By running with --parseable, only the job ID will be returned, this could save some headache.
The text was updated successfully, but these errors were encountered:
Indeed, here is an example (the argument is actually --parsable):
--parsable
> sbatch --parsable submit.job 10663264 > sbatch submit.job Submitted batch job 10663269
But I guess that will actually only change the last line in the script:
# the JOBID is the last field of the output line echo ${JOBID##* } > $LOCKFILE
that could be written as
# the JOBID is the last field of the output line echo $JOBID > $LOCKFILE
Is that correct? Is it different when a job has a dependency?
Sorry, something went wrong.
Exactly! I don't think there are any differences, sbatch just returns a job id after successful submission
No branches or pull requests
In the file https://github.com/FZJ-JSC/JUBE/blob/29aaf678069551dc6f26a775ee831852bef7d11f/platform/slurm/chainJobs.sh
The job ids are extracted after submitting to slurm. By running with --parseable, only the job ID will be returned, this could save some headache.
The text was updated successfully, but these errors were encountered: