8000 scr_run.py: exit if no jobid found by ofaaland · Pull Request #521 · LLNL/scr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

scr_run.py: exit if no jobid found #521

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
Merged
merged 1 commit into from
Dec 21, 2022
Merged

scr_run.py: exit if no jobid found #521

merged 1 commit into from
Dec 21, 2022

Conversation

ofaaland
Copy link
Contributor
@ofaaland ofaaland commented Dec 3, 2022 •
edited
Loading

We need to log the jobid for later troubleshooting, and need to be running within an allocation for operations such as scavenge.

If we cannot identify the job id, at least one of those needs is not being met, so we should exit with an error.

Also, if we are unable to identify the nodeset, include the jobid in the error message.

@ofaaland
scr_run.py: exit if no jobid found
0601716 
We need to log the jobid for later troubleshooting, and need to be
running within an allocation for operations such as scavenge.

If we cannot identify the job id, at least one of those n
89DD
eeds is not
being met, so we should exit with an error.

Also, when scr_run.py is unable to determine the nodeset, include the
jobid in the error message as that may help debug the issue.
@adammoody adammoody merged commit 418c22d into LLNL:develop Dec 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@adammoody adammoody adammoody approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ofaaland @adammoody
0