Newsgroups: php.internals,php.qa
Path: news.php.net
Xref: news.php.net php.internals:44523 php.qa:65139
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.219.223 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=n1rJYtevCEn5L7tlbXARJSnGUkN0xU2crb5z8GPfuDibWx3PMrE6p2jcLJfWdv7DVE
         mg4uQXhLtEoA9gAdWYntPwpfKaZHeLxOA2ZbLKEhCiAVZZhxgb0IMojMYGyNvIXXAAq6
         mui3SsyF9GAIF0sb53lta46LcYlkvfZFoKCY0=
Message-ID: <4A4636CD.8030604@googlemail.com>
Date: Sat, 27 Jun 2009 16:12:13 +0100
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Scott MacVicar <scott@macvicar.net>
CC: Mark Karpeles <mark@hell.ne.jp>, 
 Hannes Magnusson <hannes.magnusson@gmail.com>,
 PHP Development <internals@lists.php.net>, PHP QA <php-qa@lists.php.net>, 
 olivier@ajeux.com
References: <7f3ed2c30906261529w5103b4f6leb8dd9860aeca741@mail.gmail.com> <F7FFC613-AF9F-42E5-8094-A55EA22A81F4@macvicar.net> <1246069850.23605.12.camel@localhost> <19A8B858-410D-497B-A040-72B71FB7BEB0@macvicar.net>
In-Reply-To: <19A8B858-410D-497B-A040-72B71FB7BEB0@macvicar.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] Re: [PHP-DEV] Do you need
 different OS/platform to test on? Let "me" know
From: zoe.slattery@googlemail.com (zoe)

Hi Scott
>
> From there it can run tests and do whatever we wish with the results, 
> like grab all test failures and upload it to your test result viewer. 
> If a build fails we can have it use twitter / irc to inform people 
> that a slave failed to build PHP for whatever reason.
I wonder if we can use the new run-tests code as part of this? Georg has 
just integrated a first try at parallel running. We are working on 
having something that it's easy to grab all the test results from.

Olivier sent a note earlier this week as an attempt to map out 
requirements  what should happen with the ad-hoc test reports, however 
I'm wondering if we should just scrap the ad-hoc test reports and put 
the effort into getting results from a defined set of platforms? Aside 
from the fact that they go to a mailing list which is hard to view, 
would anyone make use of the ad-hoc reports if we could get test results 
from  a representative set of platforms in a more controlled way?

I'd like to be able to see test results across several platforms 
(various *ix, windows, mac....), 64 bit, 32 bit. And when a test fails 
to be able to get to the relevant files. This is similar to the gcov 
pages (but more) with the ability to have different views of the 
results, I like Mark's summary page but would want to be able have a few 
different views, the test fest results page has a few of the attributes 
that I'd like to see (not the color scheme of course). Is the sort of 
thing we would be able to do?
>
> It's also got various scheduling parts built in, so we can do 
> continuous regular builds to make sure its still compiling and daily 
> memory builds to check for new memory leaks.
>
> Other cool features are notifying people when it broke via IRC, 
> twitter or mailing list. And optionally packaging the freshly built 
> tests and uploading them. We could hypothetically get our snapshots 
> built this way so we never release a broken snapshot?
That would be good :-)
>
> The project URL is http://buildbot.net/trac and the vast documentation 
> is at http://djmitche.github.com/buildbot/docs/0.7.10/
>
> I might be able to sit down and give this a go on the plane next week.
Zoe