fatal errors in continuous integration environment lead to unknown result of the build

[yegor256@…]

We have CruiseControl and Phing. When there is a fatal error in our unit tests, phing crashes together with the code and do not return anything to CruiseControl. As a result, CC doesn't know the status of the build (neither success nor failure) and starts again. As a result we have an endless cycle.

I suggest to run tests (phpunit) in a separate process in order to avoid fatal crash of phing.

[mrook]

Please attach sample build files and other data to help me reproduce your issue.

[yegor256@…]

build.xml:  http://code.google.com/p/fazend/source/browse/trunk/FaZend/Application/Phing/build.xml

when crash happens in phpunit task (I mean Fatal Error) - the entire build is crashed, together with phing

[mrook]

Can you test using the latest (trunk) sources? There have been a number of fixes w.r.t. error handling in the phpunit task.

[yegor256@…]

it's a bit difficult for me since I'm installing phing by means of PEAR and there is no option (as I understand now) to install latest trunk version using PEAR, right?

maybe you could add such an option? I would love to use latest releases for testing purposes in all our projects

[mrook]

To install beta/release candidate versions of Phing thru pear, use 'pear install phing/phing-beta', for instructions on how to check out the latest trunk, see http://www.phing.info/trac/wiki/Users/Download

[FaZend <team@…>]

Would be perfect to make this possible:

pear install phing/phing-trunk

What do you think?

[mrook]

Please continue any discussion about installing trunk thru PEAR in ticket #424.