Juju CI is not testing devel branch because it claims to be a version that is released.
Juju version cannot be set to 1.19.4 https://bugs.launchpad.net/juju-core/+bug/1325074 1.19.3 is released, but the gobot fails my branch that sets the version to 1.19.4 https://code.launchpad.net/~sinzui/juju-core/inc-1.19.4/+merge/221570 This may related to the recent changes that added support for alpha/beta. We had to rollback the version because 1.18.0 throws a wobbly when the streams metadata contains a next stable with letters in the version. The test suite knows we cannot replace a published version of juju. So when devel gets updates, 1.19.3 is built because the branch claims to be 1.19.4, but the build debs are rejected because 1.19.3 really exists. The unit tests are not affected by this, just the substrate and function test are using the release 1.19.3 juju and tools. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
