Skip to content

[18.09] Fix stopping DRMAA jobs#6912

Merged
jmchilton merged 1 commit intogalaxyproject:release_18.09from
natefoo:fix-drmaa-job-stop
Oct 23, 2018
Merged

[18.09] Fix stopping DRMAA jobs#6912
jmchilton merged 1 commit intogalaxyproject:release_18.09from
natefoo:fix-drmaa-job-stop

Conversation

@natefoo
Copy link
Member

@natefoo natefoo commented Oct 23, 2018

I broke them in #6087. Also improve logging around this process.

a1c58a7 and improve logging around it.
@nsoranzo
Copy link
Member

@natefoo Wrong target branch?

@natefoo natefoo changed the base branch from dev to release_18.09 October 23, 2018 18:41
@natefoo
Copy link
Member Author

natefoo commented Oct 23, 2018

Yep thanks.

@nsoranzo
Copy link
Member

This looks good as a fix for 18.09, but I was wondering if stop_job() in BaseJobRunner and subclasses should actually receive a JobWrapper object as parameter instead of a Job object.
This should simplify this code and put the stop_job() method in line with the rest of the BaseJobRunner methods.

@natefoo
Copy link
Member Author

natefoo commented Oct 23, 2018

Yeah, that makes sense to me. In fact, all the ones receiving both the Job and JobWrapper should probably just receive JobWrapper. I think in the past the idea was that things that didn't need a JobWrapper should just get a Job since it would be quicker not to create a JobWrapper when it was unneeded.

@jmchilton
Copy link
Member

In fact, all the ones receiving both the Job and JobWrapper should probably just receive JobWrapper. I think in the past the idea was that things that didn't need a JobWrapper should just get a Job since it would be quicker not to create a JobWrapper when it was unneeded.

Perhaps it was a premature optimization - but I've sometimes passed a job parameter directly to something that had access to a job_wrapper to prevent the SA interactions in get_job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants