-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
job-runner: fix async interaction #2785
Conversation
df7dfac
to
1a7914a
Compare
It looks reasonable, works locally for me. You might find that something along the lines of |
Thanks, I just realised we already have a repo checked out that we can test, the Rose repo! Easy enough to reproduce with a local git fileinstall. |
(mac os tests squiffy ATM #2787) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, holding off merging until #2754
* The job_runner was converted to async, its tasks run in the background (i.e. calls complete before the code has finished running, you cannot await them from synchronous code). * This jiggered up some `finally` blocks which were being invoked too soon. * This PR moves the async code up one level in the stack, brining these finally blocks within the lifecycle of the job runner async code allowing them to function correctly. * Closes metomi#2784
Rebased onto master. |
(built on #2754)
Closes #2784
(hopefully this does it...)
job-runner: move finally block within async code
finally
block was run during the operation rather than after it.