Merge lp:~adeuring/charmworld/bump-charmtools-version into lp:~juju-jitsu/charmworld/trunk
Status: | Merged |
---|---|
Approved by: | Abel Deuring |
Approved revision: | 417 |
Merged at revision: | 417 |
Proposed branch: | lp:~adeuring/charmworld/bump-charmtools-version |
Merge into: | lp:~juju-jitsu/charmworld/trunk |
Diff against target: |
42 lines (+7/-4) 2 files modified
charmworld/jobs/tests/test_proof.py (+6/-3) requirements.txt (+1/-1) |
To merge this branch: | bzr merge lp:~adeuring/charmworld/bump-charmtools-version |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Gui Bot | continuous-integration | Approve | |
Brad Crittenden (community) | code | Approve | |
Review via email: mp+190648@code.launchpad.net |
Commit message
Use a version of the charmtools source tarball that includes checks of config.yaml
Description of the change
Testing the branch that was merged yesterday (lp:~adeuring/charmworld/use-charmtools-tarball), I noticed that version 1.0.1 of charmtools cannot yet check config.yaml files.
This branch changes the version of charmtools we want; I built a "private" tarball with this version -- waiting for an "official" release may need some patience...
Running the test suite, I noticed a failure in test_proof: the results of prrofing our test data changed. This failure is an implicit test that we now do indeed check the config.yaml files -- but it also shows that it was probably right to use a tarball as the source of charmtools, instead of using a reguler installation from a deb package that, originating from a PPA, might occasionally change and thus casuing unexpected test failures.
Looks good. Thanks.