On 25/07/07, Nuno Lopes <[EMAIL PROTECTED]> wrote:
So here it is my first attempt:
http://gcov.php.net/~nlopess/multi_threaded_run_tests.txt
WARNING: The patch is ugly and the output of the script isn't the prettiest.
Anyway, for automated testing seems to be good enough.
Nuno
P.S.: after this little hack, I also start to feel that run-tests.php should
be rewritten :P
""Nuno Lopes"" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Recently we have moved http://gcov.php.net to a new (and much faster)
> server. This allowed us to reduce the time to build all branches to "just"
> 2 days (compared with almost one week that would take previously).
> However I'm still not happy :P The server has 2x2 CPU cores and I would
> like to use them :) Currently I can speed-up the make process, because it
> can be parallelized (with -j xx). But the major time is still spent with
> run-tests.php.
>
> So, what I would like to propose is a multi-threaded version of
> run-tests.php. We could spawn x processes (configurable) and one of them
> would test y extensions (I think it's better to have each extension's
> tests tested serially or they may break, because they may use the same
> resources: BDs, files, etc..).
>
> Any comments?
>
> Thanks,
> Nuno
Hey Nuno, you should stop looking at things. PhD and now run-tests.
Soon you'll be taking a look at the php-src and thinking, "pah, look
what those idiots have done, time for a rewrite!". :-)
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php