Closed abentley closed 10 years ago
I think the best way to handle this is to not run charm proof against bundle charms. It's not necessary, as each charm will have been proofed individually already. I can't think of a better alternative.
A similar argument could be made for not running any charm tests when testing a bundle.
Good point, I like that even better.
When charm proof is run as a bundle test, a warning like this is always emitted:
W: metadata name (mediawiki) must match directory name (cs_precise_mediawiki-10) exactly for local deployment.
This is because proof is being run in deployer's cache directory, e.g.
/var/lib/jenkins/cloud-city/.deployer-store-cache/cs_precise_mediawiki-10