Re: QA reports interface rewrite

On Fri, May 15, 2015 at 6:49 AM, Olivier <webmaster@ajeux.com> wrote: > Hello, > > I'm reposting here a message I sent on QA mailing list a month ago with no > answer ... > > > > A few years back, I developed the "reports" interface for the QA website. > This interface is at http://qa.php.net/reports/run_tests.php > > The backend data (meaning all QA reports done with "make test") is stored > in SQLite files (one file per version). This was a requirement because the > server that hosted QA was not very powerful and with no mysql server > available. The problem is that this backend seems to suffer from > performance issues, especially when you want to have the details for a > specific version like PHP 7 (that have many reports !). > URL http://qa.php.net/reports/run_tests.php?version=7.0.0-dev > gives a 30s > timeout and a 500 error each time ... > > I'm available to double check the code if any optimization can be written, > maybe switch to a MySQL server for example if it can be done on this > specific server, and add new features (like filtering by report date. > useful for -dev version). I just need an access to the qa server to grab > the sqlite files in local and prepare the code (already have a php dev account > 'odoucet'). > > Who is in charge of this actually ? systems@php.net I'm not sure why, but all the databases are publicly indexed: https://qa.php.net/reports/db/ I opened one of the files for fun, I see no indexes there? > I also would like to provide patches to php-src so that the "make test" > process send more informations (I was waiting for the complete rewrite of > make check, but project started several years ago but never went out). That is a super conservative project. You might need a "rfc" depending on the changes: https://wiki.php.net/rfc At least mail internals@lists.php.net -Hannes