Autopilot

Long delays when running autopilot in minimal environments

Bug #1224970 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
Fix Released
Undecided
Martin Pitt
autopilot (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

In minimal environments like package build chroots or autopkgtest VMs, tests that run autopilot get stuck for some 50 seconds before the actual tests start. This doesn't happen in a fully running Ubuntu desktop session.

09:28:32.021 INFO __init__:156 - Launching process: [...]
09:28:32.033 INFO __init__:400 - dbus.DBusException while attempting to get PID for org.freedesktop.DBus: DBusException("Could not get PID of name 'org.freedesktop.DBus': no such name",)
09:28:58.203 ERROR proxies:410 - Introspect error on :1.1:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
09:28:58.204 DEBUG proxies:413 - Executing introspect queue due to error

I eventually found out that autopilot talks to bamf when you run launch_test_application(). If bamfdaemon isn't installed, you get that D-BUS timeout. We don't use bamf on touch, so I believe bamfdaemon should become a dependency of autopilot-desktop.

Related branches

lp:~pitti/autopilot/bamf-dep
Thomi Richards (community): Approve
PS Jenkins bot: Approve (continuous-integration)
Diff: 11 lines (+1/-0)
1 file modified
debian/control (+1/-0)
Martin Pitt (pitti)
Changed in autopilot:
assignee: nobody → Martin Pitt (pitti)
status: New → In Progress
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:autopilot/1.3 at revision 326, scheduled for release in autopilot, milestone Unknown

Changed in autopilot:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autopilot - 1.3.1+13.10.20130918-0ubuntu1

---------------
autopilot (1.3.1+13.10.20130918-0ubuntu1) saucy; urgency=low

  [ Jean-Baptiste Lallement ]
  * Added autopilot-sandbox-run to run autopilot tests in a 'fake' X
    server. Xephyr and Xvfb are supported. (LP: #1226070)

  [ Thomi Richards ]
  * kzgdiparg ugp srgp s r ua. (LP: #1205204)
  * Add support for click packages. (LP: #1212833)
  * Update StateNotFoundErrror exception to give more informative
    messages. (LP: #1225701)
  * Fix select_single inconsistency. (LP: #1225692)
  * Create wait_select_single method. (LP: #1223428)
  * Add test case for applications that exit with SIGABRT when launched
    with autopilot.
  * Back out changes that would break test case compatibility. (LP:
    #1226505)
  * Performance improvments for launching and closing applications under
    test with autopilot. (LP: #1218636)

  [ Andy Doan ]
  * Add support for click packages. (LP: #1212833)

  [ Christopher Lee ]
  * commit message. (LP: #1205949)

  [ Martin Pitt ]
  * Add bamfdaemon to autopilot-desktop dependencies, to avoid long
    delays when running autopilot in minimal environments. (LP:
    #1224970)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 333
 -- Ubuntu daily release <email address hidden> Wed, 18 Sep 2013 06:03:34 +0000

Changed in autopilot (Ubuntu):
status: New → Fix Released
Martin Pitt (pitti)
Changed in autopilot:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.