Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
worker/catacomb: do not deincrement catacomb.wg until worker has stopped #5578
Conversation
|
$$JFDI$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
davecheney
added some commits
Jun 9, 2016
|
$$JFDI$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit ea63958
into
juju:master
Jun 9, 2016
davecheney
deleted the
davecheney:worker-catacomb
branch
Jun 9, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
davecheney commentedJun 9, 2016
•
Edited 1 time
-
ericsnowcurrently
Jun 9, 2016
This change is a prerequisite of #5564, LP 1590161
Prior to this change, with #5564 applied, the cmd/jujud/agent tests
would reliably cause a 'session already closed' panic because the
workers owned by the catacomb had not yet stopped.
This change alters the catacomb.add logic to use the worker.Stop helper
that ensures the worker has stopped before deincrementing
catacomb.wg. In turn, assuming that the catacomb's owner waits until
its tomb is Dead, this ensures that the catacomb is not considered dead
until all its workers are fully stopped.
With this change in place, the cmd/jujud/agent tests pass reliably.
(Review request: http://reviews.vapour.ws/r/5022/)