On Mar 25, 2011, at 09:51 AM, Tres Seaver wrote: >That was precisely my proposal: when trying to check in changes to a >stdlib module, we required that developers ensure that the module's >tests, *and* those of its dependents, pass. We would need to add new >testing infrastructure to support this expectation by computing (and >saving) the dependency graph of the stdlib. I originally suggested >build time for this, but now think that it would better be built during >an intial full run of the suite.
That does seem to be a more fruitful avenue for improvement. I'm also doing more investigation into exactly why certain tests are much slower for me than for other people. The main culprit appears to be the fact that my $HOME is on an ecryptfs, so some performance hit is expected. But 600 to 25000 times slower? Hmm... Also, something seems to be not working quite right with regrtest's cd'ing to /tmp. When I build and run the tests out of /tmp (i.e. a non-ecryptfs) with -j100 it completes in under 3 minutes. Hopefully I can investigate more later today. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
