[tahoe-lafs-trac-stream] [tahoe-lafs] #1334: can't test on buildslaves that we don't depend on pywin32

[tahoe-lafs]

#1334: can't test on buildslaves that we don't depend on pywin32
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  1.9.0
     Priority:  major    |    Version:  1.8.1
    Component:  dev-     |   Keywords:  buildbot windows pywin32 review-
  infrastructure         |  needed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:10 zooko]:
 > I'm not sure if it is worth it to add complexity to
 [source:src/allmydata/__init__.py] in order to test this. We could also
 test it by having a buildslave with no pywin32 on it, right?

 No, because the part of buildbot that runs on the buildslaves depends on
 pywin32. The only other way to test this, I think, would be to make
 pywin32 available to the buildbot code without being installed, and
 without being available to subprocesses. There are two ways to do that
 that I can think of:
 a. add an entry for pywin32 to {{{sys.path}}} in the startup script for
 the buildslave;
 b. add an entry for pywin32 to {{{PYTHONPATH}}} when starting the
 buildslave (or globally), but then in the buildbot step that runs the
 Tahoe test suite, remove that entry from the {{{PYTHONPATH}}} passed to
 the subprocess.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1334#comment:11>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage