On 9/10/07, Nicholas Clark <[EMAIL PROTECTED]> wrote: > On Mon, Sep 10, 2007 at 07:39:21PM +0200, demerphq wrote: > > On 9/10/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote: > > > > Note that your test suite may or may not play nicely with that. Have > > > you ever run them in parallel before? ;-) Assuming common tempfiles > > > and such really rains on the parade. Other than that, we're talking > > > 40% less waiting. > > > > Will this make it easier to parallelize tests in the perl core? > > > > There the issue isnt so much running the tests in a single module > > directory simultaneously but rather running the tests in different > > test directories simultaneously. > > I had a hacked proof of concept for this, but it needed moderately large > changes to Test::Harness to make it work. This was around the time that the > TAPx::Parser work commenced, so it wasn't going to happen with Test::Harness > 2. > > I still *have* the proof of concept code. The key thing I needed changed was > that once you're running 2 or more tests you can't print any progress about > *the* test currently running, because your assumption that there is just one > is no longer valid. > > As to the core tests, they trip up like crazy, I think because they are not > original in their choice of names for temporary files.
When you say core tests which do you mean? The ones that test modules or the ones that test core? I guess you mean the latter, in which case I personally wouldnt be too fussed. On my machine those tests take about a minute. Its the module tests which really take a while. Especially on a threaded build Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
