> FWIW I *usually* run the test suite with parallelization (it is just so
> much quicker) and these days *rarely* see spurious failures as a result.
> This is on Mac OS X, YMMV.
I may misremember the details, but IIRC, the multiprocessing tests would
fail to terminate on Solaris. This made it unsu
Le dimanche 09 mai 2010 11:08:29, Michael Foord a écrit :
> FWIW I *usually* run the test suite with parallelization (it is just so
> much quicker) and these days *rarely* see spurious failures as a result.
> This is on Mac OS X, YMMV.
I use regrtest.py -j 4 on a Intel Quad Core on Linux: 4 tests
On 09/05/2010 03:32, Nick Coghlan wrote:
Martin v. Löwis wrote:
Has anyone considered using regrtest's -j option in the buildbot
configuration to speed up the test runs?
Yes, I did. I turned it off again when the tests started failing because
of it.
Yeah, a lot of our tests w
Martin v. Löwis wrote:
>> Has anyone considered using regrtest's -j option in the buildbot
>> configuration to speed up the test runs?
>
> Yes, I did. I turned it off again when the tests started failing because
> of it.
Yeah, a lot of our tests weren't written with parallel execution in mind
(e.
> Has anyone considered using regrtest's -j option in the buildbot
> configuration to speed up the test runs?
Yes, I did. I turned it off again when the tests started failing because
of it.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.o
Hi,
> Has anyone considered using regrtest's -j option in the buildbot
> configuration to speed up the test runs?
Perhaps some buildbots are doing other useful tasks, in addition to
simply building Python. This should probably be a case by case setting.
I don't know how easy it is to add specif
