[Bug 21937] Tests shouldn't take 5 minutes to run

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 20 12:28:22 CEST 2009


http://bugs.freedesktop.org/show_bug.cgi?id=21937


Dafydd Harries <dafydd.harries at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dafydd.harries at collabora.co.
                   |                            |uk




--- Comment #1 from Dafydd Harries <dafydd.harries at collabora.co.uk>  2009-08-20 03:28:22 PST ---
Ideas:

 - Eliminate reactor.iterate() call, either by switching to a new API, or using
some cunning producer/consumer system. I have a branch working on the former
(test-api-3); I tried the latter once, but had problems with serializing
events.
 - Profile with gprof/oprofile.
 - Run tests in parallel. Each test definitely needs a connection to itself,
and maybe a CM to itself (which would mean a bus to itself).

I thought maybe that Python startup time (including imports etc.) was a
bottleneck, but I wrote a test runner that in theory made all startup costs a
one-off cost and it only shaved off ~30s.

What's our goal, assuming the current number of tests? One minute? Two?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the telepathy-bugs mailing list