Merge lp:~veebers/juju-ci-tools/record_timing_actions into lp:juju-ci-tools
Proposed by
Christopher Lee
Status: | Merged |
---|---|
Merged at revision: | 1982 |
Proposed branch: | lp:~veebers/juju-ci-tools/record_timing_actions |
Merge into: | lp:juju-ci-tools |
Prerequisite: | lp:~veebers/juju-ci-tools/juju_timing_reporting |
Diff against target: |
192 lines (+43/-17) 5 files modified
jujupy/client.py (+27/-5) jujupy/tests/test_client.py (+6/-6) jujupy/tests/test_version_client.py (+4/-4) jujupy/version_client.py (+2/-1) tests/test_deploy_stack.py (+4/-1) |
To merge this branch: | bzr merge lp:~veebers/juju-ci-tools/record_timing_actions |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Aaron Bentley (community) | Approve | ||
Review via email: mp+321354@code.launchpad.net |
This proposal supersedes a proposal from 2017-03-28.
Commit message
Enable collection of timing data for bootstrap, kill/destroy controller and deploy.
Description of the change
Enable collection of timing data for bootstrap, kill/destroy controller and deploy.
Timing collection for bootstrap and kill/destroy controller are collected without any need for any intervention from a test author.
deploy on the other hand needs to make a change where instead of:
client.
client.
Instead:
_, deploy_complete = client.deploy(...)
client.
The resulting timing data looks like: http://
To post a comment you must log in.
It seems strange CommandComplete objects for synchronous operations. I think we only need that for asynchronous ones. Why do you want this?