[tahoe-lafs-trac-stream] [tahoe-lafs] #20: unit tests take too long

[tahoe-lafs]

#20: unit tests take too long
------------------------+------------------------------
     Reporter:  zooko   |      Owner:  somebody
         Type:  defect  |     Status:  reopened
     Priority:  major   |  Milestone:  eventually
    Component:  code    |    Version:
   Resolution:          |   Keywords:  test performance
Launchpad Bug:          |
------------------------+------------------------------

Comment (by zooko):

 Oh wait, did I say 20%? I changed my mind. To get my 50ⓑ, you have to make
 it 5X faster—in other words take 20% of the total runtime—on Brian's
 laptop.

 Note that Brian's laptop has some kind of performance problem with disk
 I/O, such that unit tests take about 24 minutes on there, compared to
 these runtimes on our buildslaves:

 https://tahoe-lafs.org/buildbot-tahoe-lafs/builders/lucid-amd64/builds/58

 12 minutes

 https://tahoe-lafs.org/buildbot-tahoe-
 lafs/builders/Atlas%20ubuntu%20natty/builds/65/steps/test

 15 minutes

 https://tahoe-lafs.org/buildbot-tahoe-
 lafs/builders/Ruben%20Fedora/builds/65

 13 minutes

 https://tahoe-lafs.org/buildbot-tahoe-
 lafs/builders/Kyle%20OpenBSD%20amd64/builds/72

 10 minutes.

 So you might be able to win by finding figuring out where our unit tests
 are relying on disk I/O and replacing those unit tests with in-memory fake
 objects. That would almost certainly not lose coverage over any line of
 code.

 I probably won't change my mind again for at least a few days, so get
 crackin'!

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/20#comment:14>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage