Comment 8 for bug 1993533

Revision history for this message
George Kraft (cynerva) wrote :

That's my understanding, yes. Adam updated our test suite to libjuju 3.0.1[1][2], worked through some initial issues that included updating our unit.run calls to have the newly needed await[3], encountered and reported the action issue I mentioned before[4], then reverted us back to libjuju 2.9.11[5]. I'll ask Adam to look at this thread in case he has any further details that might help.

[1]: https://github.com/charmed-kubernetes/jenkins/pull/976
[2]: https://github.com/charmed-kubernetes/jenkins/pull/978
[3]: https://github.com/charmed-kubernetes/jenkins/pull/982/files#diff-ba7b4974291be4e7299ba770949340a1e2c2fb9b3a22d6d16cac8f1d0187c4d9R532-R533
[4]: https://github.com/juju/python-libjuju/issues/719
[5]: https://github.com/charmed-kubernetes/jenkins/pull/987