MacOS X Test Failures

[bewst]

Build looks good, but python setup.py test gives the following. It's still running but all the tests marked [ERROR] seem to be taking forever and then, perhaps, timing out. Partial log attached.

[bewst]

log of python setup.py test

[bewst]

Heh, interesting: I got past ​that first traceback by preceding the test by "sudo" (should that really be necessary?) but that doesn't seem to change what happens around test_download_abort_if_too_many_missing_shares, which is a bunch of errors and a big slowdown.

[zooko]

Thank you very much for the bug report.

Hmmm. Is this Mac OS 10.6? There is a known bug in pycryptopp on that platform. (The current trunk of pycryptopp has that bug fixed, so you could try installing the current trunk of pycryptopp and see if that fixes it.)

The permission error with "dropin.cache.new" is described here:

​http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#WhydoIgetaPermissiondeniederrortryingtowrite...site-packagestwistedpluginsdropin.cache.newwhenIusetwistdortrialorsomeotherTwistedprogram

Running the whole test with "sudo" is definitely not right, and perhaps you ought to now do something to repair any damage, such as sudo chown -R `whoami` .. :-)

Could you please attach the _trial_temp/test.log file from the failing test?

[bewst]

Replying to zooko:

Thank you very much for the bug report.

Hmmm. Is this Mac OS 10.6?

Yes, it is.

There is a known bug in pycryptopp on that platform. (The current trunk of pycryptopp has that bug fixed, so you could try installing the current trunk of pycryptopp and see if that fixes it.)

I'll do that.

Could you please attach the _trial_temp/test.log file from the failing test?

As soon as I install a fixed pycryptopp.

[zooko]

The current release of pycryptopp -- v0.5.17 -- works on Mac OS 10.6.

[davidsarah]

Should the version requirement in _auto_deps.py be updated to "pycryptopp >= 0.5.17"?

[zooko]

Hm. I hate to impose that constraint on platforms where they don't need the newer pycryptopp. pycryptopp-0.5.17 is necessary for Mac OS 10.6 and for Fedora amd64, and it may or may not be needed for other Linux amd64. pycryptopp-0.5.15 is necessary for AthlonXP and old-style Celeron.

Also note that the latest pycryptopp-0.5.17 won't build properly with the brand new Ubuntu Karmic: ​https://bugs.launchpad.net/ubuntu/+bug/461303 .

Anyway, maybe we should increase that requirement, or do so on the known-to-be-affected platforms. I'd like to put it off and think about it for a bit first, though. For one thing, we have a recurring problem with people being unable to install Tahoe-LAFS because they can't install pycryptopp. One of the main ways that I intend to address that problem is for buildslaves to build binary libraries ("eggs") of pycryptopp and upload them to here: ​http://allmydata.org/source/tahoe/deps/tahoe-dep-eggs . The idea is that the Tahoe-LAFS build system (using setuptools) will automatically download the appropriate binary egg from that list for the platform on which it is building.

That mechanism basically works, but we haven't set up buildslaves for all the right platforms and all of the dependencies and tested it out.

[zooko]

I guess we should configure _auto_deps.py to require pycryptopp >= 0.5.17 if the platform is Mac OS X or is 64-bit Linux and to require pycryptopp >= 0.5.15 if not.

[daira]

The current pycryptopp dependency is >= 0.6.0, so this is probably no longer an issue.