You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a tasks is creating qsub jobs for every sample in an analysis, and one sample causes an exception to be raised, the remaining qsub jobs might not be killed if they are not in the background jobs list yet. Need to look into method for handling this
The text was updated successfully, but these errors were encountered:
maybe give each task object its own internal job queue to put jobs into and monitor from, and wrap a try ... except around the task running itself, catch if exception is raised and run a task.kill_jobs() method similar to the function used in job_management
convert the job_management module into a JobManager object class, use one for monitoring the pipeline background jobs and add them to each task to monitor jobs
If a tasks is creating qsub jobs for every sample in an analysis, and one sample causes an exception to be raised, the remaining qsub jobs might not be killed if they are not in the background jobs list yet. Need to look into method for handling this
The text was updated successfully, but these errors were encountered: