-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-04-18 02:04 PM, John Meinel wrote:
I did eventually manage to run the CI tests, though there are some
oddities:
Sorry about that. The top-level 'upgrade-job' and 'deploy-job'
scripts were never meant to run locally. Originally, we entered
I did eventually manage to run the CI tests, though there are some oddities:
1) You have to set JUJU_HOME and SCRIPTS, though that is in the docs
2) You have to set LOCAL_JENKINS_URL to the ec2 instance
3) You have to set WORKSPACE, but you *also* have to have $PWD already be
in WORKSPACE.
4)
I'm not sure what happened, because r2655 shows it passing on all targets,
but the actual change was only really related to MaaS.
I'm still going to try and see if I can get the CI tests to run locally. If
I can get the steps to set up pretty clear, then it should be easier for us
to reproduce
lp:juju-core/trunk r2644 introduced a regression.
upgrade-juju fails on all providers
https://bugs.launchpad.net/juju-core/+bug/1309108
Unit agents are not upgrading. I attacked logs from all the failed tests.
--
Curtis Hovey
Canonical Cloud Development and Operations
