Re: Improvements and glitches for make test

Hi,

On Thu, 2010-04-22 at 13:04 +0300, Miroslav Kubelík - seznam wrote:
> Hello,
> when I have started to develop extensions (one year ago) with phpize,  
> there was
> no possibility to use another php.ini unless default (which is specified
> via ./configure for whole php installation). This made problem when

./run-tests.php -c /path/to/php.ini

> "make test" was used in new extension development dir. PHP complained
> for extensions which was specified in default php.ini and weren't
> in "modules" subdir under new extension dir. So I had to copy
> all my "productions" extensions to every "modules" subdir under each
> newly developed extension dir.

Maybe it's worth to allow multiple extension dirs, distributors might
like that, too.

> When I upgrade to 5.3.2, there is newly created tmp-php.ini always
> when I type phpize, this isn't mentioned anywhere (maybe I overlooked?).
> Is this a fix? Is used for phpized "make test"?

It is a fix and always used, not only in phpize'd builds. But we have a
bad track record documenting internals.

> And in 5.3.2 is a new glitch with "make test" and phpize. Everytime when
> test fails, there is a request for sending response to QA with test result.
> I don't remember this is 5.3.0-1 and with phpize (extension development)
> it doesn't make sense to send result of my extension tests to QA.

Feel free to provide a nice patch for run-tests :-)

johannes