You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least on noble, when run on a laptop that is not plugged in, features/api/unattended_upgrades.feature will fail when looking for a non-null last_run value. It fails because the unattended-upgrade will refuse to run when not connected to power.
Expected behavior
This test should either pass when not connected to power, or fail loudly with a clear explanation that it requires being connected to power.
Current behavior
The test fails when looking for a non-null value with no indication that it is not due to a bug.
To Reproduce
Unplug your laptop
tox run -e behave -- features/api/unattended_upgrades.feature -D releases=noble -D machine_types=lxd-container
The text was updated successfully, but these errors were encountered:
Description of the bug
At least on noble, when run on a laptop that is not plugged in, features/api/unattended_upgrades.feature will fail when looking for a non-null
last_run
value. It fails because the unattended-upgrade will refuse to run when not connected to power.Expected behavior
This test should either pass when not connected to power, or fail loudly with a clear explanation that it requires being connected to power.
Current behavior
The test fails when looking for a non-null value with no indication that it is not due to a bug.
To Reproduce
tox run -e behave -- features/api/unattended_upgrades.feature -D releases=noble -D machine_types=lxd-container
The text was updated successfully, but these errors were encountered: