On Thu, Oct 07, 2004 at 04:04:16PM -0400, Geoffrey Young wrote:
hi all...
just FYI, 2.1 is failing t/modules/proxy.t with a 404. I've spent some time this afternoon trying to see what (of importance) has changed in between 2.0 and HEAD but I can't see where it is at the moment.
I don't know who else is running nightly regression tests here. I have
I run a lot of them, but not all the time as it makes my notebook smoke. I do only 2.0 and test against all perl versions 5.6.1 - 5.9.1, each perl built in 4 different ways, plus one apache worker and one apache prefork.
just synched the results from the builds I started running with httpd+mod_perl-from-CVS on a few machines here:
http://www.apache.org/~jorton/regress/mod_perl.html
I know these are not entirely useful without access to the machines to debug etc but it does at least give status tracking.
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.
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.
-- __________________________________________________________________ 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]
