On Sat, May 31, 2014 at 9:42 AM, Matteo Beccati <p...@beccati.com> wrote:
> Hi everyone, > > I've finished upgrading the Bamboo CI instance for the Revive Adserver > project (previously known as OpenX Source, phpAdsNew, etc) in order to > also run unit and integration tests with the very latest versions of php > coming straight from git. The main purpose is to get an early notice if > some of the commits breaks the project or causes segmentation faults. > > As a by-product, we have the daily results of the PHP test suite running > publicly available here: > > https://revive.beccati.com/bamboo/browse/PHP-SRC > > Tests are run for master, 5.4, 5.5, 5.6, phpng and the int64 branch. At > the moment all the builds are failing. > > On master there are 6 tests (some zend_multibyte-*.phpt and > pdo_mysql_prepare_emulated.phpt) with warnings (XFAIL section but test > passes), plus a gd test failing and 3 new failures in the dom extension, > since I've upgraded to libxml 2.9.1+dfsg1-3ubuntu2.1 yesterday[1]: > > https://revive.beccati.com/bamboo/browse/PHP-SRC-10/test > > Other branches have more / different failures. For those not familiar > with Bamboo, you can switch branches with the "master" dropdown above. > > This is not meant to be a replacement for the current Travis setup, but > hopefully a welcome addition. If someone is interested, I can add their > email address to the notification list. > > > [1] https://launchpad.net/ubuntu/+source/libxml2/2.9.1+dfsg1-3ubuntu2.1 > It appears that a security update disabled the feature required in such > tests. > > > Cheers > -- > Matteo Beccati > > Development & Consulting - http://www.beccati.com/ > > -- > PHP Quality Assurance Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > > Hi, thanks for the work. we also have http://ci.qa.php.net/ and it used to build and execute userland projects and their testsuite (symfony2, etc.), but then the hosting provider shut down the box without prior notice, so I had to recreate the box from scratch and never really find the time to finish it. I've also noticed that you did a couple of changes about the junit.xml output of run-tests.php, I have to look into those, because at the moment the parsing of the junit.xml fails on the jenkins box with the following error: *11:14:32* [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'junit.xml' relative to '/var/lib/jenkins/workspace/php-src-5.5/cpu_architecture/amd64/os_distribution/ubuntu/os_family/linux' for the testing framework 'JUnit'.*11:14:32* [xUnit] [ERROR] - The result file '/var/lib/jenkins/workspace/php-src-5.5/cpu_architecture/amd64/os_distribution/ubuntu/os_family/linux/junit.xml' for the metric 'JUnit' is not valid. The result file has been skipped. ps: personally I wouldn't choose bamboo four ourselves, because it is a closed-source, proprietary product, and doesn't really provide any important feature versus the current leading floss products, but I think the more tools we can use for catching the bugs, the better. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
