No easy way to profile the vis tool.

Bug #1279944 reported by Thomi Richards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
Fix Released
High
Unassigned
autopilot (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The autopilot vis tool is slow - we must be making some blocking calls somewhere. Unfortunately, due to the way we launch the vis tool, you cannot enable profiling using the standard:

python -m cProfile -o vis.profile <scriptname>

So we should add support to enable tracing the vis tool as a command line option. something like:

autopilot vis --enable-tracing <output_file>

should do the trick...

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autopilot - 1.4+14.04.20140219-0ubuntu1

---------------
autopilot (1.4+14.04.20140219-0ubuntu1) trusty; urgency=low

  [ Thomi Richards ]
  * Vis tool improvements for self-testing: Added ability for vis tool
    to be run with testability enabled, and able to be profiled. (LP:
    #1279944)
  * Add a decorator that makes it easy to write compatible __repr__
    functions in both python 2.x and 3.x.

  [ Leo Arias ]
  * Refactor the _uinput module to avoid side-effects when we import it.
  * Added Mouse, Touch and Pointer drags with rate. (LP: #1257055)

  [ Max Brustkern ]
  * Handle trailing slashes on suites. (LP: #1199088)

  [ Christopher Lee ]
  * Fix import error in functional test
    test_bamf_geometry_gives_reliable_results. (LP: #1281253)

  [ CI bot ]
  * Fix test_command_line_args issues with python 3.4. (LP: #1281733)
 -- Ubuntu daily release <email address hidden> Wed, 19 Feb 2014 21:41:38 +0000

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

Other bug subscribers

Remote bug watches

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