FTBFS: AsyncExecutionLoadTest.RepeatedlyInvokingAnAsyncFunctionWorks fails: Current count of 378 does not match 500
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus-cpp |
New
|
Undecided
|
Unassigned |
Bug Description
From https:/
Builds of dbus-cpp for several architectures (armhf, mips, mipsel, and
the non-release architectures alpha and x32) failed with errors along
the lines of
15/15 Test #1: async_execution
Running main() from gmock_main.cc
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from AsyncExecutionL
[ RUN ] AsyncExecutionL
dbus[25970]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/114" not available: No such file or directory
/<<BUILDDIR>
Value of: ec->wait_
Actual: false (Current count of 378 does not match 500)
Expected: true
dbus[25966]: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered
[ FAILED ] AsyncExecutionL
[----------] 1 test from AsyncExecutionL
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (300015 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] AsyncExecutionL
1 FAILED TEST
93% tests passed, 1 tests failed out of 15
Total Test time (real) = 300.02 sec
The following tests FAILED:
1 - async_execution
Errors while running CTest
Presumably, these architectures' autobuilders happen to lack /run/user.
(I'm just tagging the two affected mips architectures for now, as
presumably representative here.)
-
Can we skip this test if /run/user does not exist?
> dbus[25970]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/114" not available: No such file or directory
This is not the root cause of the test failure. On the Debian bug, Aurelien Jarno comments that official Debian autobuilders (on which dbus-cpp passed its tests) have the same setup with a nonexistent /run/user.
dbus-daemon will log this message if XDG_RUNTIME_DIR is set to a nonexistent directory, but if dbus-cpp is not using the transient service directory feature, the warning is harmless. In practice it seems unlikely to need that feature.