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.

Sign up for GitHub

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

Jump to bottom

Updated content from discourse for term slurm #25

Open
manbat opened this issue Feb 28, 2020 · 0 comments
Open

Updated content from discourse for term slurm #25

manbat opened this issue Feb 28, 2020 · 0 comments

Comments

@manbat
Copy link
Member

manbat commented Feb 28, 2020

Is there a command/option you can run to determine the specifics of why a SLURM job is still pending execution besides the REASON CODE given by the squeue command (with default options)? E.g. What resources is it waiting on and/or what currently running/pending jobs might be competing for those resources?

CURATOR: Jack Smith

See Full Post
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@manbat