I don't think any changes in the code would cause the error we're seeing. I think I know what may be up...
If you look at the last good build, and the first failed one: http://ci.apache.org/builders/log4php-trunk/builds/232/steps/compile/logs/stdio http://ci.apache.org/builders/log4php-trunk/builds/233/steps/compile/logs/stdio The environment is changed. Someone has been messing around with the buildbot and probably broke something for us. Looking at the PATH, someone changed it so that /home/gmcdonald/bin is in the path before /usr/bin and /usr/local/bin... This may mean that we're including the wrong phpunit, as you suspected. Can you maybe contact Gavin and ask him what's up? Regards, Ivan On 22 March 2012 10:34, Christian Grobmeier <[email protected]> wrote: > Ok.... anybody has got an idea on that? > Not sure... did it always take the phpunit out from Gavins home? > Somehow I doubt... > Commits recently which might kill this build? > > Cheers > Christian > > unit-testing: > [mkdir] Created dir: > /home/buildslave1/slave1/log4php-trunk/build/target/surefire-reports > [mkdir] Created dir: > /home/buildslave1/slave1/log4php-trunk/build/target/site/coverage-report > [exec] > [exec] Fatal error: Call to undefined method > PHPUnit_Util_Filter::addFileToFilter() in /home/gmcdonald/bin/phpunit > on line 46 > [exec] > [exec] Call Stack: > [exec] 0.0002 637368 1. {main}() /home/gmcdonald/bin/phpunit:0 > [exec] > [exec] Result: 255 > > > On Thu, Mar 22, 2012 at 4:56 AM, <[email protected]> wrote: >> The Buildbot has detected a new failure on builder log4php-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/log4php-trunk/builds/233 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: ceres_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch logging/log4php/trunk] 1302163 >> Blamelist: >> >> BUILD FAILED: failed compile >> >> sincerely, >> -The Buildbot >> >> >> > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de
