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

COMPLETED_SUCCESSFUL is set in BE.ExecutionService when qsub exited with 0 #117

Open
vinjana opened this issue May 17, 2018 · 0 comments
Open

COMPLETED_SUCCESSFUL is set in BE.ExecutionService when qsub exited with 0 #117

vinjana opened this issue May 17, 2018 · 0 comments
Labels
bug
Milestone
Release 1.0

Comments

@vinjana
Copy link
Contributor

vinjana commented May 17, 2018

Original at: TheRoddyWMS/Roddy#222

COMPLETED_SUCCESSFUL is set by BE.ExecutionService, when the execution result is successful, i.e. the qsub, not when the job finished successfully on the cluster!

COMPLETED_SUCCESSFUL is meant to be the state of a successfully finished job, not successful submission! The proper status should therefore be just SUBMITTED.

Write the correct status line in Roddy.Job.appendToJobStateLogfile()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
The BatchEuphoria Project
Status: Backlog
Milestone
Release 1.0
Development

No branches or pull requests
1 participant
@vinjana