Re: QA Reports aggregator

Hello, The advantage of my tool is that it's currently working :) I just need to setup the sqlite3 db and it will be OK (working great in local). user reports are already aggregated (code commited). My first setup of the db contains all reports sent by users in the last 30 days. Code is available here :http://svn.php.net/viewvc/web/qa/trunk/reports/ Connector is here : http://svn.php.net/viewvc/web/qa/trunk/buildtest-process.php?view=co Where is the rmtool code ? I will be glad to take a look and see how we can merge our efforts. Olivier 2011/5/20 Hannes Magnusson <hannes.magnusson@gmail.com> > On Fri, May 20, 2011 at 15:46, Pierre Joye <pierre.php@gmail.com> wrote: > > On Fri, May 20, 2011 at 3:37 PM, Hannes Magnusson > > <hannes.magnusson@gmail.com> wrote: > >> On Fri, May 20, 2011 at 15:08, Pierre Joye <pierre.php@gmail.com> > wrote: > >>> Hi Olivier, > >>> > >>> Something along this line is what we have been working on for some > >>> time already with the rmtools (/rmtools in SVN). > >>> > >>> rmtools include tools to build php and report the log and to run the > >>> tests. For the tests we have implemented it for our custom tests > >>> (which run through web servers and cli, and are slightly more complex > >>> than simple phpt) and include performance regressions. > >>> > >>> Maybe we could share our work and integrate what you have done so far > >>> into rmtools? Doing so will have the great advantage to make it work > >>> immediately for any new branch and later for pecl as well. > >>> > >>> The goal is to have one place where RMs and developers can quickly > >>> check that everything is fine in a current branch, on all platforms. > >> > >> > >> The key difference is that the rmtools build process tests different > >> architectures and in a controlled environment. > >> The 'make tests' user submitted results are in an uncontrolled > >> environment, on all sorts of possible wacky configuration and > >> platforms. > > > > > > There is no difference in how they work. One single place to control > > everything is way more easier to work with and to maintain. It is > > critical as well to integrate revisions in the results and the delta > > between them. > > > Where can I find the test execution results currently? > > -Hannes >