devel almost fixed
Curtis Hovey-Canonical
curtis at canonical.com
Wed Aug 13 14:09:46 UTC 2014
Mages, shamans, and practitioners of high mana magic.
All critical bugs affecting stable and devel are fixed, but devel has
yet to passed CI. Sorry.There was a bout of cloud failures that I
discounted by replaying the tests. run-unit-tests-precise-amd64 failed
4 times in a row, but the test failures are not consistent. I haven't
filed a bug as yet. A new revision is building and I hope that all
tests will pass this time. The devel branch has not passed tests since
2014-06-25, 49 days ago.
Several AWS tests were retried because EC2 reported there were no IPs
available at the time. We want to make CI smart enough to recognise
this and schedule the retry itself.
I reported https://bugs.launchpad.net/juju-core/+bug/1356363 about
Azure not providing the vnet. This looks like an Azure issue. In the
future, we might need to make juju more robust in this situation.
The Failed unit tests are:
http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-amd64/1459/console
http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-amd64/1458/console
http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-amd64/1457/console
http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-amd64/1456/console
--
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui
More information about the Juju-dev
mailing list