commit/galaxy-central: natefoo: Handle Pulsar job stop when setting metadata remotely.
1 new commit in galaxy-central: https://bitbucket.org/galaxy/galaxy-central/commits/77e633e92604/ Changeset: 77e633e92604 User: natefoo Date: 2014-09-05 17:41:05 Summary: Handle Pulsar job stop when setting metadata remotely. Affected #: 1 file diff -r be2c86442b3e28407d7b845a90420c3feb3fe859 -r 77e633e926043524691dcc193f3e7d59809d06a8 lib/galaxy/jobs/runners/pulsar.py --- a/lib/galaxy/jobs/runners/pulsar.py +++ b/lib/galaxy/jobs/runners/pulsar.py @@ -416,8 +416,9 @@ def stop_job( self, job ): #if our local job has JobExternalOutputMetadata associated, then our primary job has to have already finished + client = self.get_client( job.destination_params, job.job_runner_external_id ) job_ext_output_metadata = job.get_external_output_metadata() - if job_ext_output_metadata: + if not PulsarJobRunner.__remote_metadata( client ) and job_ext_output_metadata: pid = job_ext_output_metadata[0].job_runner_external_pid # every JobExternalOutputMetadata has a pid set, we just need to take from one of them if pid in [ None, '' ]: log.warning( "stop_job(): %s: no PID in database for job, unable to stop" % job.id ) Repository URL: https://bitbucket.org/galaxy/galaxy-central/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email.
participants (1)
-
commits-noreply@bitbucket.org