On Thu, 21 Jun 2001, Stas Bekman wrote:
> ------------------
> Run:
> $ ./t/TEST --run-tests
> $ ./t/TEST --run-tests modules/cgi.t
>
> the second time modules/cgi.t is run, test #3 fails.
i see that too, not looked into it yet.
> Me thinking: if the test reports ok on the first run, but fails on the
> second, should we change the way tests are run? rerun tests
> twice to make sure that the test really passes
> ? more times? how about stress testing option?
t/TEST --run-tests=n
where n would be the number of times to run all the tests would be cool.
for certain tests such as the ones that currently fail twice, we can just
hardwire a for (1,2) {} in the .t
> I'm trying to debug handlers from ./t/response via 'print STDERR' ,
> but nothing ever gets to the error_log file (I did check the file
> descriptor and it points to the correct error_log).
it might be buffered. what about warn() ?
> (Doug, my configuration/build opts don't change so unless you tell me
> otherwise I won't repost it every time. the options are from
> mod_perl_dev.pod anyway.)
sure, that's fine.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
