From 8623e277b4a5f2f98f9daa1f412da1a74aa05f9c Mon Sep 17 00:00:00 2001 From: Matthias Bernt Date: Tue, 28 Jun 2022 12:04:38 +0200 Subject: [PATCH] JobWrapper: use correct fail method if the JobWrapper.fail method is called directly exit code (etc) are lost. fixes https://github.com/galaxyproject/galaxy/issues/14206 not sure why this error popped up now, probably a change in tool verification ..? --- lib/galaxy/jobs/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/galaxy/jobs/__init__.py b/lib/galaxy/jobs/__init__.py index b6d99043ebad..0bedace7b3d5 100644 --- a/lib/galaxy/jobs/__init__.py +++ b/lib/galaxy/jobs/__init__.py @@ -1796,7 +1796,7 @@ def fail(message=job.info, exception=None): else: # Prior to fail we need to set job.state job.set_state(final_job_state) - return self.fail(f"Job {job.id}'s output dataset(s) could not be read") + return fail(f"Job {job.id}'s output dataset(s) could not be read") job_context = ExpressionContext(dict(stdout=job.stdout, stderr=job.stderr)) if extended_metadata: