Merge lp:~jameinel/juju-core/bad-formatting-1216285 into lp:~go-bot/juju-core/trunk
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | John A Meinel | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 1723 | ||||
Proposed branch: | lp:~jameinel/juju-core/bad-formatting-1216285 | ||||
Merge into: | lp:~go-bot/juju-core/trunk | ||||
Diff against target: |
176 lines (+137/-1) 4 files modified
environs/tools/tools.go (+1/-1) environs/tools/tools_test.go (+19/-0) testing/checkers/log.go (+60/-0) testing/checkers/log_test.go (+57/-0) |
||||
To merge this branch: | bzr merge lp:~jameinel/juju-core/bad-formatting-1216285 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email:
|
Commit message
environs/tools: print out the correct version
Bug #1216285 is because we were miss-formatting a line about what
version we were filtering. It turns out that while we were printing out
an int as "%s" we were also not priting out what the filter would
actually match. (If you pass a version in that field, we match the exact
version, not just the major version.)
In the process, I realized we don't have much infrastructure for testing
what log messages we are writing, so I added a LogMatches checker. I
think it is something that actually fits better inside the loggo
package, but I wanted to give it some real experience before I tried to
get it into upstream.
Description of the change
environs/tools: print out the correct version
Bug #1216285 is because we were miss-formatting a line about what
version we were filtering. It turns out that while we were printing out
an int as "%s" we were also not priting out what the filter would
actually match. (If you pass a version in that field, we match the exact
version, not just the major version.)
In the process, I realized we don't have much infrastructure for testing
what log messages we are writing, so I added a LogMatches checker. I
think it is something that actually fits better inside the loggo
package, but I wanted to give it some real experience before I tried to
get it into upstream.
Reviewers: mp+181983_ code.launchpad. net,
Message:
Please take a look.
Description:
environs/tools: print out the correct version
Bug #1216285 is because we were miss-formatting a line about what
version we were filtering. It turns out that while we were printing out
an int as "%s" we were also not priting out what the filter would
actually match. (If you pass a version in that field, we match the exact
version, not just the major version.)
In the process, I realized we don't have much infrastructure for testing
what log messages we are writing, so I added a LogMatches checker. I
think it is something that actually fits better inside the loggo
package, but I wanted to give it some real experience before I tried to
get it into upstream.
https:/ /code.launchpad .net/~jameinel/ juju-core/ bad-formatting- 1216285/ +merge/ 181983
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/12744051/
Affected files: tools/tools. go tools/tools_ test.go checkers/ log.go checkers/ log_test. go
A [revision details]
M environs/
M environs/
A testing/
A testing/