[
https://issues.apache.org/jira/browse/LOG4PHP-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234971#comment-13234971
]
Bruce Ingalls edited comment on LOG4PHP-174 at 3/22/12 2:48 PM:
---
On Thu, Mar 22, 2012 at 10:55 AM, Ivan Habunek wrote:
> 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/co
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/buil
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
