Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47017
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.78.25 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=U1ASfvKRgdMc85r8arL2ZKNU9eRgcOy6KSQDy8tcc5EkdDT1zdp5sG1CDo2m2obM/U
         3u8XCJ6pYF6Ab8AvVIcJ75OeI3QQEqXI8mWTkxD708+k9LBbjLEMTZc+hHNJOczeYSN8
         sImJYJHQ1CXPKU58BIUdT2HkVs4TA5+9Q+ad4=
MIME-Version: 1.0
In-Reply-To: <fe05d1541002220020n4b8d4e10ka373e23b045bd5f4@mail.gmail.com>
References: <F2.C8.00376.AC9D18B4@pb1.pair.com>
	 <fe05d1541002220020n4b8d4e10ka373e23b045bd5f4@mail.gmail.com>
Date: Mon, 22 Feb 2010 09:21:50 +0100
Message-ID: <fe05d1541002220021q3009af8cu7da18e17e40a6341@mail.gmail.com>
To: Raphael Geissert <geissert@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] multi-jobs run-tests.php
From: pierre.php@gmail.com (Pierre Joye)

forgot to add the link to the repo:

http://svn.php.net/viewvc/php/phpruntests/

On Mon, Feb 22, 2010 at 9:20 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> hi,
>
> There is an on-going work on run-test (which began as part of last
> year GSoC). I would begin there instead of working on the current
> run-test.php. Parallel testing is part of the new features as well, in
> a portable way (like not only where pcntl is available).
>
> Thanks for your work,
>
> Cheers,
> --
> Pierre
>
> On Mon, Feb 22, 2010 at 2:11 AM, Raphael Geissert <geissert@php.net> wrote:
>> Hi,
>>
>> I've spent the last hours working on making run-tests.php be able to run
>> tests in parallel. The main reason being the time it takes to run the whole
>> testsuite even on multicore CPUs.
>>
>> Attached is the first set of changes needed. It uses pcntl's fork and
>> sysvmsg to send some of the results back to the parent process.
>>
>> Main functionalities still work, but the summary doesn't include failed
>> tests.
>>
>> I plan to move away from sysvmsg because with the current implementation
>> killing the parent process can leave message queues open (nothing that can't
>> be fixed by adding a proper exit handler) and sysvmsg is not enabled by
>> default. Probably to something php://memory-based.
>>
>> To support all the features under multi-jobs mode I think the proper fix is
>> to cleanup the code so that run_test() stores the state information via an
>> interface. This would make the code cleaner and would let multi-jobs mode
>> just change the state-storing interface.
>>
>> How should I handle this? just by committing the changes? first sending them
>> here (to internals)? by contacting somebody else?
>>
>> Cheers,
>> --
>> Raphael Geissert
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
>
>
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org