I submitted a job yesterday in the afternoon. It was supposed to be fast (sent as a dataset collection of two datasets, with an expected execution time of five minutes maximum more or less).
Seeing that it was still running after a while, I was a bit surprised, but since I noticed some uncommonly long running times on some of my jobs last week in a way that seemed random, I just let it for a while.
Be this morning I saw that it was still running... It took a closer look at it, and it seems the jb is resummitted again and again and again, explaining why it is still running...
Any idea what might happen here?
- I used the same module on another dataset collection in another history, and it ran smoothly
- It can happen sometimes that some of my job are killed "by an administrator". When it happens, I rerun it and can get the expected green result. Not sure it has anything to do with this issue but still saying in case there could be a link in a way or another.
"Still running" job metadata:
|Galaxy Tool ID:||toolshed.g2.bx.psu.edu/repos/lecorguille/xcms_xcmsset/abims_xcms_xcmsSet/3.6.1+galaxy0|
|Galaxy Tool Version:||3.6.1+galaxy0|
|Tool Standard Output:||stdout|
|Tool Standard Error:||stderr|
|Tool Exit Code:||None|
|History Content API ID:||a4a98aad5abb77d6|
|Job API ID:||409cc46b87aae3f5|