-
Notifications
You must be signed in to change notification settings - Fork 622
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.
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
OAR - HOLD status instead of waiting status #2540
Comments
Still not clear why NF should fail. Since hold is considered running, it should continue to wait indefinitely |
I'm going to investigate too. (Note that the task is "completed", and exit is "-") nextflow/modules/nextflow/src/main/groovy/nextflow/processor/TaskProcessor.groovy Line 2147 in 38bef6c
Here a more complete trace:
|
"Nextflow believes that job is running, and is locking looking for output files but is unable to find expected files" => not true. It's just a side effect, not the root cause of the program to stop |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug report
In rare cases, nextflow may stop because of job state incoherency with OAR. Indeed, OAR seems to set job status to HOLD during a very short time at its creation. (https://github.com/oar-team/oar/blob/4860ba9b0a592be5682a56635aa22e11bc705d84/sources/core/common-libs/lib/OAR/IO.pm#L1710)
Actual behavior
Nextflow believes that job is running, and is
lockinglooking for output files but is unable to find expected files. This stops the program.Program output
Environment
Additional context
Related issue
The text was updated successfully, but these errors were encountered: