On Sep 24, 2010, at 10:40 AM, David Mintz wrote:
> Still getting this rude behavior. I might try posting to the ZF list. I think
> it's conceivable that something in ZF is squandering memory, even though PHP
> is supposed to manage memory for us. I will also try upgrading my ZF.
>
> If I ever ge
On Fri, Sep 24, 2010 at 10:42 AM, Chuck Reeves wrote:
> If you run the site outside of phpunit, do you still get the memory error?
>
>
Never. Thanks for asking the obvious question.
--
David Mintz
http://davidmintz.org/
It ain't over:
http://www.healthcare-now.org/
__
If you run the site outside of phpunit, do you still get the memory error?
Thank You
Chuck Reeves
Cell: 631-374-0772
Email: chuck.ree...@gmail.com
On Fri, Sep 24, 2010 at 10:40 AM, David Mintz wrote:
>
>
> On Thu, Sep 23, 2010 at 1:27 PM, Rob Marscher
> wrote:
>
>> On Sep 23, 2010, at 12:44 P
On Thu, Sep 23, 2010 at 1:27 PM, Rob Marscher wrote:
> On Sep 23, 2010, at 12:44 PM, David Mintz wrote:
> > Gee, this is interesting:
> >
> > da...@interps3:/opt/www/shitou/tests$ phpunit -d memory_limit 256M
> --verbose
> >
> > Fatal error: Allowed memory size of 262144 bytes exhausted (tried to
On Sep 23, 2010, at 12:44 PM, David Mintz wrote:
> Gee, this is interesting:
>
> da...@interps3:/opt/www/shitou/tests$ phpunit -d memory_limit 256M --verbose
>
> Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate
> 4864 bytes) in
> /usr/share/downloads/ZendFramework-
On Thu, Sep 23, 2010 at 12:29 PM, Rob Marscher
wrote:
> On Sep 23, 2010, at 12:23 PM, David Mintz wrote:
> > I have upped the memory limit to 64M in both /etc/php5/apache2/php.ini as
> well as /etc/php5/cli/php.ini. Same story: still bonking without emitting an
> error message, even with that outp
On Sep 23, 2010, at 12:23 PM, David Mintz wrote:
> I have upped the memory limit to 64M in both /etc/php5/apache2/php.ini as
> well as /etc/php5/cli/php.ini. Same story: still bonking without emitting an
> error message, even with that output buffering turned off.
Hmm... you can also pass a cust
On Thu, Sep 23, 2010 at 10:26 AM, Rob Marscher
wrote:
> Let us know what it was when you find it.
>
I have a bootstrap.php in which I inserted an ob_start() a long time ago,
because for reasons I don't entirely understand, I was getting errors about
sending cookie headers after some other output
Check to make sure that all of your test files have at least one test in
them. Most of the time when PHP Unit has failed for me, that has been the
main reason.
If you are calling setUp or tearDown, make sure you call the parent ones as
well (This is vital if you are using the database test case).
On Sep 23, 2010, at 10:18 AM, David Mintz wrote:
> It would be a PITA but I guess I could start removing test classes/files one
> by one until I isolate the offender. Bleh.
Yeah... I had that happen before and ended up putting echo statements into my
test suite to figure out what test it was fai
On Wed, Sep 22, 2010 at 12:00 PM, Chuck Reeves wrote:
> Do you have any test classes that are missing test methods?
> Also turn on error_reporting since PHPunit cannot catch fatal errors
>
> Thanks for the suggestion.
I cranked up error_reporting to E_ALL and found a couple of 'undefined
index' w
Do you have any test classes that are missing test methods?
Also turn on error_reporting since PHPunit cannot catch fatal errors
Thank You
Chuck Reeves
Cell: 631-374-0772
Email: chuck.ree...@gmail.com
On Wed, Sep 22, 2010 at 11:55 AM, David Mintz wrote:
> Just wondering if any of you PHPUnit a
Just wondering if any of you PHPUnit and/or Zend Framework ninjas have any
insight into this.
When I simply run the command 'phpunit' from the top level of my tests
directory, it seems the process somehow silently pukes. It wasn't always
thus; I added a couple more test classes and this started be
13 matches
Mail list logo
