Have updated packaging and upstream for both juju 2.0 and 1.25 ready to
upload.


https://code.launchpad.net/~juju-qa/ubuntu/xenial/juju/juju-1.25.5

New 1.25.5 bugfix release. Fixed the adt tests, including making them
run with isolation-container rather than isolation-machine.

adt-run [18:19:14]: @@@@@@@@@@@@@@@@@@@@ summary
client               PASS
current-local-provider PASS
future-local-provider PASS
current-manual-provider PASS
future-manual-provider PASS

Final note, I have for now reverted the dependency change to use juju-
mongodb2.6 as upstream code doesn't correctly detect its existence and
continues to use juju-mongodb (2.4) anyway. I will follow up with a bug
against 1.25.6 for this.


https://code.launchpad.net/~juju-qa/ubuntu/xenial/juju/xenial-2.0-beta4

New 2.0-beta4 release. Fixed a bunch of issues with the tests, including
the requirement for manual lxd configuration. Unfortunately, lxd
currently doesn't work in the nested container setup of these tests, so
I have not been able to verify everything works yet.

adt-run [23:53:12]: @@@@@@@@@@@@@@@@@@@@ summary
current-lxd-provider SKIP Test requires machine-level isolation but testbed 
does not provide that
client               PASS
current-manual-provider PASS
future-manual-provider PASS

The juju-2.0 package now recommends lxd as suggested.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to