Autopilot FTBFS during override_dh_auto_test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopilot (Ubuntu) |
Fix Committed
|
High
|
Richard Huddie |
Bug Description
A rebuild of autopilot on zesty (1.4.1+
The actual failure:
HOME=`mktemp -d --tmpdir=debian` \
XDG_RUNTIME_
python3 -m testtools.run discover autopilot.
/usr/lib/
warn(
terminate called after throwing an instance of 'std::runtime_
what(): Unable to connect to user bus: Cannot autolaunch D-Bus without X11 $DISPLAY
Aborted (core dumped)
debian/rules:23: recipe for target 'override_
Related branches
- Santiago Baldassin (community): Approve
- platform-qa-bot: Approve (continuous-integration)
-
Diff: 87 lines (+14/-7)1 file modifiedautopilot/tests/unit/test_application_launcher.py (+14/-7)
Changed in autopilot (Ubuntu): | |
assignee: | nobody → Richard Huddie (rhuddie) |
status: | New → In Progress |
Changed in autopilot (Ubuntu): | |
status: | In Progress → Fix Committed |
After doing some blind experimenting, trying a build with an attached DISPLAY=:0.0 before the actual test command the build still fails with: "what(): Unable to connect to user bus: Failed to execute child process “dbus-launch” (No such file or directory)". Installing dbus-x11 (which has dbus-launch) makes it go forward but then I get some test failures that fail the build. Besides, I don't think built-time unit tests should really depend on having a graphical stack - certainly I wouldn't want to add the dbus-x11 build-dep without a really good reason.
Could anyone take a look at this?