Ron Schmidt via RT wrote: >> It'd be nice if we used the same env var for this as we did for the >> main harness. (that one is currently TEST_JOBS, iirc.) > > Per request from moritz I have come up with an updated patch that seems > to apply cleanly and tested it on Ubuntu and cygwin/Windows Vista. It > gives the expected output for "make test" and "make spectest" in both > cases and gives a nice performance boost under Ubuntu.
Thank you very much. On Debian with two cores I get 2 jobs: 4m04 1 job: 2m35 Which is good enough for me ;-) > Under > cygwin/Windows Vista however the performance seems a bit slower and I > wonder if we shouldn't really check for the OS or use 'jobs:1' in > languages/perl6/t/harness rather than 'jobs:3'. Is there a good reason to test in parallel at all if TEST_JOBS isn't set as an environment? That's how perl and parrot core tests do it, and I think it's quite a good practice. People who test often will just define that environment variable globally. > Per the suggestion above the controlling environment variable in the > patch is TEST_JOBS. ++ for that, and ++ for the patch. Now we need some feedback from MacOS X and windows/msvc users, then I'll apply the patch. Cheers, Moritz -- Moritz Lenz http://moritz.faui2k3.org/ | http://perl-6.de/
