Skip to content
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

Implement verdi work kill #821

Merged
merged 15 commits into from
Oct 23, 2017

Conversation

sphuber
Copy link
Contributor

@sphuber sphuber commented Oct 20, 2017

Fixes #661

This also requires changes in plum and so will need a new support release v0.7.10 of plum.
This has not yet been released and therefore has not been added to the setup_requirements.py yet.

greschd and others added 13 commits October 17, 2017 12:38
For WorkCalculations to be abortable through the kill() method
the abort sequence of the Process had to be changed a bit. Upon
abort, the ABORTED key will be set on the calculation node and
the process will be put in the STOPPED state through .stop()
The on_destroy method will check the state of the calculation
and seal it when appropriate. The other point where the node
can be sealed is in the ProcessFinaliser which will be hit if
the process fails during a tick
The has_aborted check was added for WorkCalculations but the
JobCalculations have no concept of an abort and therefore it
was excepting in the on_destroy.
Copy link
Contributor

@muhrin muhrin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bangin.

@muhrin muhrin merged commit 5d9e389 into aiidateam:release_v0.10.0 Oct 23, 2017
@sphuber sphuber deleted the fix_661_verdi_work_kill branch October 23, 2017 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/critical-blocking must be resolved before next release topic/workflows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants