are_queued_jobs_finished.py getting stuck #12622
Assignees
Labels
Comments
milljm
added a commit
to milljm/moose
that referenced
this issue
Dec 18, 2018
The 'are_queued_jobs_finished.py' script is not doing anything specific when error 271 occures. So why not just exit if the very presence of 'Exit_status' exists in the first place? Closes idaholab#12622
milljm
added a commit
to milljm/moose
that referenced
this issue
Dec 18, 2018
The 'are_queued_jobs_finished.py' script is not doing anything specific when error 271 occurs. So why not just exit if the very presence of 'Exit_status' exists in the first place? Closes idaholab#12622
milljm
added a commit
to milljm/moose
that referenced
this issue
Jan 7, 2019
A darn typo slipped through. Closes idaholab#12622
shoheiogawa
pushed a commit
to shoheiogawa/moose
that referenced
this issue
Jan 18, 2019
The 'are_queued_jobs_finished.py' script is not doing anything specific when error 271 occurs. So why not just exit if the very presence of 'Exit_status' exists in the first place? Closes idaholab#12622
shoheiogawa
pushed a commit
to shoheiogawa/moose
that referenced
this issue
Jan 18, 2019
A darn typo slipped through. Closes idaholab#12622
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rationale
If the TestHarness runs into an exception during a PBS submission, this script will return 1. Meaning any other script waiting for a 0 (all queued jobs have completed), will never happen.
Description
A TestHarness exception causes are_queued_jobs_finished.py to exit incorrectly.
Impact
Low
The text was updated successfully, but these errors were encountered: