Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47027
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.134 as permitted sender)
To: Raphael Geissert <geissert@php.net>
Cc: internals@lists.php.net
In-Reply-To: <5F.B8.00376.7C5B28B4@pb1.pair.com>
References: <F2.C8.00376.AC9D18B4@pb1.pair.com>
	 <fe05d1541002220020n4b8d4e10ka373e23b045bd5f4@mail.gmail.com>
	 <5F.B8.00376.7C5B28B4@pb1.pair.com>
Content-Type: text/plain; charset="UTF-8"
Organization: php.net
Date: Mon, 22 Feb 2010 18:12:07 +0100
Message-ID: <1266858727.3086.533.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] multi-jobs run-tests.php
From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2010-02-22 at 10:50 -0600, Raphael Geissert wrote:
> Ah, I see, great. 
> >From a quick look at the code it looks like it also uses pcntl.
> 
> Is there any plan to switch to that other implementation?
> 
> No work has been done in something like the threads extension, has there?

Why would you need threads? - Won't some async process control be
enough? - The test manager doesn't have to be parallelized, it should
just run multiple tests at once. And yes, I'm very interested I have a
64 way SPARC machine which currently needs 7 days for a gcov run which,
in theory, might be reduced to 7/64 days ...

Another interesting thing might be directory-wide skipif so we don't
have to run two PHP interpreters per test.

But when working on all kinds of things there one should look on the
rewrite by Zoe (and others) which should be nicer for modification than
the grown code of the existing run-tests.php

johannes