The Linux integration tests were skipped since we started installing
python-dbusmock by hand, which meant that package dependencies like
python3-gobject were never installed, and the whole test would be
skipped.
Fixes: 3acbedca26
We need a higher than default timeout as the
test_critical_action_is_taken_repeatedly test takes at least 2 suspend
cycles and those take at least UP_DAEMON_ACTION_DELAY (20 seconds).
The daemon sources and libupower-glib were built without their historic
log domains which meant some debug messages did not appear when running
upowerd in verbose mode.
This fixes the test_no_poll_batteries test.
We don't care that the up_exported_kbd_backlight_* symbols and functions
were removed from the libupower-glib ABI, they should never have been
exported in the first place as this API is only used server-side, in the
daemon.
77 is the special value meaning that the test was skipped. Both meson
make check will display the information correctly.
Note that the test is currently executed directly in check-local. So add
a workaround to ignore the 77 error code and exit 0 instead in that
case.
Inhibitor lock should be taken between the critical
action notification and the execution of the critical action.
Requires python-dbusmock > 0.23.1, test is skipped on lower versions.
python-dbusmock in the CI is installed from git and bumped version
to 0.23.2 until a new release is available.
Phones are suspended most of the time so they are not awake for > 20s
to allow UPower to take action when battery is critical.
Add an interface to take and release inhibitor locks which
prevent the device from suspending to allow UPower to execute
the critical power action.
gudev 234 had bugs converting cached sysfs properties to boolean which
caused upower to think that batteries were not there, as the "present"
sysfs attribute was misread.
Require at least gudev 235 to avoid battery detection being broken.
Closes: #149
USB PD 3.1 allows up to 240W (48V, 5A) and some proprietary supplies
already delivered more than 100W over USB-C (USB PD 3.0 limit).
Closes: #147
Reported by StefanBruens
If we want the computer to be able to take useful action about the low
battery, we should have a slightly higher "low" percentage level so that
power saving made really makes a difference in runtime.
Also bump "critical" slightly so that doom isn't quite as near but in the
distance nonetheless.
The "action" level stays the same, as 1% is too close to some batteries'
actual switch off point, eg. the computer might brown out before we see
1%.
