Merge lp:~bac/charms/precise/juju-gui/1086790 into lp:~juju-gui/charms/precise/juju-gui/trunk
Proposed by
Brad Crittenden
Status: | Merged |
---|---|
Approved by: | Gary Poster |
Approved revision: | 9 |
Merged at revision: | 9 |
Proposed branch: | lp:~bac/charms/precise/juju-gui/1086790 |
Merge into: | lp:~juju-gui/charms/precise/juju-gui/trunk |
Diff against target: |
226 lines (+90/-14) 9 files modified
config.yaml (+8/-1) hooks/install (+28/-12) hooks/start (+1/-0) hooks/stop (+1/-0) hooks/utils.py (+27/-0) revision (+1/-1) tests/deploy.test (+1/-0) tests/test_utils.py (+22/-0) tests/unit.test (+1/-0) |
To merge this branch: | bzr merge lp:~bac/charms/precise/juju-gui/1086790 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gary Poster (community) | Approve | ||
Benji York (community) | code | Approve | |
Review via email: mp+138823@code.launchpad.net |
Description of the change
Add command-level logging in the hooks. Also for the run('make') command, stdout and stderr are redirected to a separate file so that progress can be monitored as it occurs. None of the other commands are long running to require that level of detail.
Sorry for not using Rietveld but I could not get lbox to work with this target.
To post a comment you must log in.
The branch looks good. I only had small suggestions or questions.
The "#-*- python -*-" on line 28 surprised me. I am not against that
style of file type markers, but I just wanted to be sure it was
intentional. Oh, and it would be nice if there were a space after the
"#" character. :)
The import on line 130 could be a single-line import.
Line 164: hmm, prefixing the string with a newline will mean that the
log file starts with a blank line. That's not the end of the world, but
it is a bit odd. Maybe a comment to explain why would be in order.
Line 171 of the diff, the contents of the revision file: I /think/ I
saw a recent branch that bumped the revision higher than 13. You might
want to double-check what number the trunk is on.
Line 206: "The monkey patch is undone at the end of the test." Should
that read "The monkey patch is undone in the tearDown method."?