Skip to content
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

Possible improvement for ChainJobs #17

Open
thijssnelleman opened this issue Dec 9, 2024 · 2 comments
Open

Possible improvement for ChainJobs #17

thijssnelleman opened this issue Dec 9, 2024 · 2 comments

Comments

@thijssnelleman
Copy link

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.

@filipesmg
Copy link
Contributor

Indeed, here is an example (the argument is actually --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?

@thijssnelleman
Copy link
Author

Exactly! I don't think there are any differences, sbatch just returns a job id after successful submission

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants