Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
A new runner for DRMAA (currently UNIVA) #7004
Reimplementation of the DRMAA runner inspired by the SLURM runner. Currently tested only for the UNIVA grid engine (but I'm optimistic that it should work as well for other drmaa systems).
This solves the problem that the current DRMAAJobRunner does not work when jobs are submitted as real user (because jobs that are started in a different drmaa session can not be accessed from the session that is open in galaxy):
Furthermore (in contrast to the original drmaa runner) the new one tests for run time and memory violations:
Open (or better perspective):
The changes in drmaa.py do not change the functionality at all, but only reorganize the code. In particular part of the function
referenced this pull request
Nov 12, 2018
No. Slurm-drmaa is for SLURM clusters (which use sacct,... for querying jobs). univa-drmaa is for clusters running UNIVA grid engine (which use qacct,... for querying) -- but I guess it also works for SUN grid engine (but I can not test this).
Both SlurmJobRunner and UnivaJobRunner derive from DRMAAJobRunner which can not be used in the setting that submits jobs as the real user. This is because the (python) drmaa library can only query jobs that are created in the same drmaa session, but in the real user setting jobs are started by an external script (
The solution of SlurmJobRunner and UnivaJobRunner is to use the corresponding command line tools to query the job state.
I do not understand this question.