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.
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 /github. com/charmed- kubernetes/ jenkins/ pull/978 /github. com/charmed- kubernetes/ jenkins/ pull/982/ files#diff- ba7b4974291be4e 7299ba770949340 a1e2c2fb9b3a22d 6d16cac8f1d0187 c4d9R532- R533 /github. com/juju/ python- libjuju/ issues/ 719 /github. com/charmed- kubernetes/ jenkins/ pull/987
[2]: https:/
[3]: https:/
[4]: https:/
[5]: https:/