The only thing blocking k8s integration testing with libjuju 3.0.0 is [issue-719][1] where
# run a command on a unit:
action = await ubuntu.units[0].run("sleep 30")
before = datetime.now()
# await that result
result = await action.wait()
# Rather than getting a "completed" -- we get pending?
assert result.success == "completed", "Shouldn't be 'pending' -- only completed or failed"
after = datetime.now()
# (after - before) should be >= 30 seconds, but instead its far less.
libjuju doesn't actually await the result of the long running command
We can modify one line to test out a new release of libjuju [here][2]
The only thing blocking k8s integration testing with libjuju 3.0.0 is [issue-719][1] where
# run a command on a unit: units[0] .run("sleep 30")
action = await ubuntu.
before = datetime.now()
# await that result
result = await action.wait()
# Rather than getting a "completed" -- we get pending?
assert result.success == "completed", "Shouldn't be 'pending' -- only completed or failed"
after = datetime.now()
# (after - before) should be >= 30 seconds, but instead its far less.
libjuju doesn't actually await the result of the long running command
We can modify one line to test out a new release of libjuju [here][2]
[1]: https:/ /github. com/juju/ python- libjuju/ issues/ 719 /github. com/charmed- kubernetes/ jenkins/ blob/main/ jobs/integratio n/utils. py#L598- L603
[2]: https:/