-
Notifications
You must be signed in to change notification settings - Fork 2
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
any way to help when sbatch/srun exit immediately because of invalid submission #2
Comments
Incorrect job submission parameters are definitely an issue in general, but That being said, I have a couple ideas:
For the |
Use of |
Right, so there could be an |
Yeah, I like the "mistake analyzer" idea, though not sure what the interface would be exactly. |
I'm imagining it just hooks into the shell so then immediately after |
Even for jobs that get queued, if they violate a constraint, ideally we would warn the user upon submission rather than wait for them to wonder why the job isn't starting. Here are some examples from running squeue today of jobs that are just sitting there because of too many cores for savio_long, too long a time limit, and too many cpus for a given condo.
Related to your mistake analyzer idea but would presumably need to be triggered in a different way. |
Here's a standard use case that is not amendable to use of
sq
because the job exits immediately.@nicolaschan any ideas of how we might help users in such cases?
This case is missing
-c 2
.The text was updated successfully, but these errors were encountered: