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

HOLD status on new job and OARSTAT #190

Open
grafitos opened this issue Sep 2, 2021 · 0 comments
Open

HOLD status on new job and OARSTAT #190

grafitos opened this issue Sep 2, 2021 · 0 comments

Comments

@grafitos
Copy link

grafitos commented Sep 2, 2021

Hello oarteam,

As I can see in IO.pm, new jobs are created with "hold" state first (why not using special state?), then they are updated to "waiting" state.

It seems that oarstat is not aware of this "trick", and can lead to strange behavior in some cases when oarstat is called in this very short time event (hold->waiting). (State transition HOLD->WAITING with some workflow framework like NextFlow can stop script execution with an error).

Could you please confirm the behavior?
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
@grafitos