Merge lp:~1chb1n/charm-helpers/amulet-relations-settled into lp:charm-helpers
| Status: | Work in progress |
|---|---|
| Proposed branch: | lp:~1chb1n/charm-helpers/amulet-relations-settled |
| Merge into: | lp:charm-helpers |
| Diff against target: |
63 lines (+46/-0) 1 file modified
charmhelpers/contrib/amulet/utils.py (+46/-0) |
| To merge this branch: | bzr merge lp:~1chb1n/charm-helpers/amulet-relations-settled |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Ryan Beisner | Disapprove on 2015-07-13 | ||
| Corey Bryant (community) | 2015-07-02 | Approve on 2015-07-09 | |
| James Page | 2015-07-02 | Pending | |
| Liam Young | 2015-07-02 | Pending | |
|
Review via email:
|
|||
Description of the Change
Add check_hooks_
Prior to this, openstack amulet tests relied on an arbitrary sleep time after deployment returned "complete," to wait for hooks to settle. That was racey, as the sleep time was not always enough during higher testing load.
This proposal uses the logic that openstack-
# Charm test MPs which depend on this landing:
https:/
| Ryan Beisner (1chb1n) wrote : | # |
| Ryan Beisner (1chb1n) wrote : | # |
For reference, this is based on juju_check_
| Corey Bryant (corey.bryant) wrote : | # |
Looks good but I have a couple comments.
| Ryan Beisner (1chb1n) wrote : | # |
Thanks, see replies, questions in line.
| Corey Bryant (corey.bryant) wrote : | # |
Responded inline
- 402. By Ryan Beisner on 2015-07-09
-
Plumb timeout all the way through;
Remove 2nd _remote_runs check;
Adjust _remote_run failure feedback.
- 403. By Ryan Beisner on 2015-07-13
-
add 2nd _remote_runs check back in
| Ryan Beisner (1chb1n) wrote : | # |
FYI, with the 2nd remote run check removed, the test race condition re-appeared. So I added it back, which also keeps the approach in line with the same in openstack mojo specs.
| Corey Bryant (corey.bryant) wrote : | # |
Sounds fine to me then.
- 404. By Ryan Beisner on 2015-07-13
-
rebase
| Ryan Beisner (1chb1n) wrote : | # |
Abandoning this as the juju run twice approach appears to no longer be effective.
I disapprove. ;-)
Unmerged revisions
- 404. By Ryan Beisner on 2015-07-13
-
rebase
- 403. By Ryan Beisner on 2015-07-13
-
add 2nd _remote_runs check back in
- 402. By Ryan Beisner on 2015-07-09
-
Plumb timeout all the way through;
Remove 2nd _remote_runs check;
Adjust _remote_run failure feedback. - 401. By Ryan Beisner on 2015-07-02
-
add juju_hooks_complete to amulet/utils.py (based on openstack-
mojospecs)


FYI: To check the new wait logic, I repeatedly ran multiple simultaneous jobs while the system was under load, and all passed.
http:// 10.245. 162.77: 8080/view/ Dashboards/ view/Amulet/ job/charm_ amulet_ test/4993/ 10.245. 162.77: 8080/view/ Dashboards/ view/Amulet/ job/charm_ amulet_ test/4994/ 10.245. 162.77: 8080/view/ Dashboards/ view/Amulet/ job/charm_ amulet_ test/4995/ 10.245. 162.77: 8080/view/ Dashboards/ view/Amulet/ job/charm_ amulet_ test/4996/ 10.245. 162.77: 8080/view/ Dashboards/ view/Amulet/ job/charm_ amulet_ test/4997/
http://
http://
http://
http://