On Tue, May 1, 2012 at 3:46 PM, Dannon Baker <dannonba...@me.com> wrote:
>On Tue, May 1, 2012 at 3:10 PM, Peter Cock <p.j.a.c...@googlemail.com> wrote:
>> On May 1, 2012, at 10:03 AM, Dannon Baker <dannonba...@me.com> wrote:
>> > On May 1, 2012, at 9:51 AM, Peter Cock wrote:
>> >
>> >> I'm a little confused about tasks.py vs drmaa.py but that TODO
>> >> comment looks pertinent. Is that the problem here?
>> >
>> > The runner in tasks.py is what executes the primary job, splitting
>> > and creating the tasks.  The tasks themselves are actually injected
>> > back into the regular job queue and run as normal jobs with the
>> > usual runners (in your case drmaa).
>> >
>> > And, yes, it should be fairly straightforward to add, but this just hasn't
>> > been implemented yet.
>> >
>> > -Dannon
>> So the stop_job method for the runner in task.py needs to call the
>> stop_job method of each of the child tasks it created for that job
>> (which in this case are drmaa jobs - but could be pbs etc jobs).
>> I'm not really clear how all that works.
>> Should I open an issue on this?
>> Peter
> I'll take care of it.  Thanks for reminding me about the TODO!

Hi Dannon,

Is this any nearer the top of your TODO list? I was reminded by having
to manually log onto our cluster today and issue a bunch of SGE qdel
commands to manually kill a job which was hogging the queue, but
had bee deleted in Galaxy.



Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:


Reply via email to