Fwd: [Canonical-juju-qa] Cursed (final): #1529 gitbranch:1.20:github.com/juju/juju ee834020 (run-unit-tests-precise-amd64, run-unit-tests-precise-i386, run-unit-tests-trusty-amd64, run-unit-tests-trusty-ppc64el, run-unit-tests-utopic-amd64)

[Ian Booth]

The issue is that we do not allow upload-tools for non-dev versions of Juju and
until now, unit tests had always been run with version.Current set to a dev
version. Now that we have created a release candidate branch and flipped the
version to 1.20, the issue arose.

The fix was to patch the version number in the 2 failing tests. This has been
done in other tests but not the 2 which failed.

https://github.com/juju/juju/pull/191




On 28/06/14 06:03, Curtis Hovey-Canonical wrote:
> ---------- Forwarded message ----------
> From: CI & CD Jenkins <aaron.bentley+cjqa at canonical.com>
> Date: Fri, Jun 27, 2014 at 3:51 PM
> Subject: [Canonical-juju-qa] Cursed (final): #1529
> 
> 
> Build: #1529 Revision: gitbranch:1.20:github.com/juju/juju ee834020
> Version: 1.20.0
> 
> Failed tests
> run-unit-tests-precise-amd64 build #1034
> http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-amd64/1034/console
> run-unit-tests-precise-i386 build #264
> http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-i386/264/console
> run-unit-tests-trusty-amd64 build #1049
> http://juju-ci.vapour.ws:8080/job/run-unit-tests-trusty-amd64/1049/console
> run-unit-tests-trusty-ppc64el build #651
> http://juju-ci.vapour.ws:8080/job/run-unit-tests-trusty-ppc64el/651/console
> run-unit-tests-utopic-amd64 build #180
> http://juju-ci.vapour.ws:8080/job/run-unit-tests-utopic-amd64/180/console
> 
> All the unit tests are broken. I reported
> https://bugs.launchpad.net/juju-core/+bug/1335243
> Looks like juju is looking for 1.2.0, 2 not 20.
>