Thanks for the bug report, that is indeed a problem - I am not sure
how the torque runner here would ever reach a complete job state. I
prefer the following fix however, if you would be willing to verify it
fixes the problem you are encountering I would be happy to apply it to
Galaxy's stable
Hi,
base:
os:centos6.4
torque:4.2.7
I built a glaxy cluster today,and then I found the job completion status of
torque queue is 'c',but the need state of galalxy is ok.So I modified the
torque.py file and solved this error. I do, right?
diff -r 8411a9f30feb
