{"push_id":908620407,"size":1,"distinct_size":1,"ref":"refs/heads/FLOC-3665-cleanup-nodes-on-cluster-failure","head":"e46f72808aba8a3069214ad21839f61c922554c4","before":"08b597ddca5807b84aa416b667b583a45852feb3","commits":[{"sha":"e46f72808aba8a3069214ad21839f61c922554c4","author":{"email":"e8fcfaece79eb0a9f94e1b0d264e9c0133020411@clusterhq.com","name":"Andriy Gapon"},"message":"run-acceptance-tests: make cluster clean up more robust\n\nBecause main() is decorated with @inlineCallbacks there is no guarantee\nthat the control flow always returns to it after a yield statement.\nIn particular, that's the case if the reactor is stopped.\nAnd that could happen, for instance, if a user presses Ctrl-C because\ntwisted installs a SIGINT handler which stops the reactor.\n\nThus, to improve the chances of the cluster clean-up being executed\nthe clean-up code is moved to a before-shutdown system event trigger.\n\nAlso, we now destroy the cluster if we couldn't finish its setup\neven if --keep option is set.","distinct":true,"url":"https://api.github.com/repos/ClusterHQ/flocker/commits/e46f72808aba8a3069214ad21839f61c922554c4"}]}