[tahoe-dev] [tahoe-lafs] #853: unit tests hang on Windows (pycryptopp related?) (was: networking failures on WinXP)

[tahoe-lafs]

#853: unit tests hang on Windows (pycryptopp related?)
--------------------------------+-------------------------------------------
 Reporter:  zooko               |           Owner:           
     Type:  defect              |          Status:  new      
 Priority:  major               |       Milestone:  undecided
Component:  code-network        |         Version:  1.5.0    
 Keywords:  windows pycryptopp  |   Launchpad_bug:           
--------------------------------+-------------------------------------------

Comment(by zooko):

 Okay I moved the issue about {{{route.exe}}} not being found over to a new
 ticket: #854 (what to do when you can't find any IP address for yourself).

 This ticket is now renamed to "unit tests hang on Windows (pycryptopp
 related?)".  Let me see if I understand what has been reported so far:

  * Kai reports the unit test process hangs or spins at
 {{{allmydata.test.test_checker.WebResultsRendering.test_check}}} using the
 official "python.org" Python 2.6.4 (from http://www.python.org/download/ )
 on Windows XP SP3 32-bit. His {{{test.log}}} doesn't have anything useful
 in it.  Kai: would you please turn on verbose logging (
 http://allmydata.org/trac/tahoe/browser/docs/logging.txt ) and try again?
  * Grumpf reports "I had to manually install pycryptopp patching his
 config.h, disabling assembler parts (#define CRYPTOPP_DISABLE_ASM) in
 order to pass tahoe tests.". Grumpf: what happens if you do not manually
 install pycryptopp and patch his {{{config.h}}}?  Does Tahoe-LAFS fail to
 build?  Does it build but fail its unit tests?  If so in what way?  Also
 could you please run the pycryptopp unit tests.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/853#comment:12>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid