| Summary: | sys-power/upower fails tests (needs a running dbus system bus) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Freedesktop bugs <freedesktop-bugs> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | QA | CC: | nikoli |
| Priority: | High | Keywords: | TESTFAILURE |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | Restricted in ebuild | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Build log
devkit-power-0.14.diff |
||
|
Description
Diego Elio Pettenò (RETIRED)
2010-05-04 18:29:36 UTC
Created attachment 230325 [details]
Build log
The failure is the same if you enable tests in upower ebuild: /power/backend: *** ERROR *** TI:16:11:37 FI:up-device.c FN:up_device_init,888 - error getting system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory FAIL: up-self-test I wonder if there is a way to have a test dbus system daemon running to satisfy this kind of testsuite. Let's convert this bug to sys-power/upower one, since it's RESTRICT'd there and because sys-apps/devicekit-power is obsolete. ok, starting a custom instance of dbus and setting DBUS_SYSTEM_BUS_ADDRESS to say: unix:path=${T}/test_system_bus_socket works.
The test suite even succeeds if the daemon is running as nobody.
Created attachment 249087 [details, diff]
devkit-power-0.14.diff
This patch makes it work. It feels a bit dirty though, so I'm open to suggestions on how to make it nicer.
oh and adaptation to upower should be trivial shouldn't have click "submit anyway", sorry. they look to pass for 0.99.3, please recheck with that |