On Fri, Oct 08, 2004 at 10:08:21AM -0400, Stas Bekman wrote:
And it'd be nice for the failing test to run t/REPORT and include it in the output. W/o it we know almost nothing about what perl and apache builds were used.
I guessed you'd say that... I've changed the script to append ./t/REPORT and tail -100 t/logs/error_log if the tests fail.
There is a better way, instead of 'make test' run t/SMOKE -bug and it'll show the failing STDOUT and STDERR only for those tests that have failed (it seeks through both streams after each test is run). It also scans for core files (which makes it quite slower than plain t/TEST, but it tells you exactly which test has caused the segfault). The only problem is that it's not an equivalent of make test (yet). perhaps we should make a new target for it. For now you need to run:
t/TEST -conf t/SMOKE -bug cd ModPerl-Registry t/TEST -conf t/SMOKE -bug
and then you only need to add the output of t/REPORT
Also this fails to build: http://www.apache.org/~jorton/regress/2004-10-05/cocoa/mod_perl-on-2.0-make.log
^^^^^^^^^^but you aren't using the current cvs, where it was fixed :) so other reports are probably failing for the same reason.
You missed the time axis at the top :)
But I also didn't remember when it was fixed :)
I just went to see if I can fix the problems :)
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
