> I don't know who else is running nightly regression tests here. I have > 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
very cool. what are you using to generate that? for the curious, here's what I have been running nightly. current mod_perl CVS against: 2.0.47-worker-perl-5.8.5 2.0.52-worker-perl-5.8.5 2.1-worker-perl-5.8.5 2.1-prefork-perl-5.8.5 2.1-prefork-perl-5.8.5-nothreads 2.0-worker-perl-5.8.0 2.0-worker-perl-5.8.5 2.0-prefork-perl-5.8.0 2.0-prefork-perl-5.8.5 2.0-prefork-perl-5.8.5-nothreads > I know these are not entirely useful without access to the machines to > debug etc but it does at least give status tracking. yup. and if each of us done it a little bit different we'll be catching different stuff. for instance, all my builds use MP_COMPAT_1X=0, which is not the default and has caught a few little things. and, until you reported it, I think I was the only one testing 2.1 nightly - thanks for the help :) >>so, if anyone has been following proxy development of late and knows what >>the issue is, feel free to jump in. otherwise, just know that I'm working >>on it. > > > I presumed this was because of all the recent proxy/balancer type > changes... yeah, I saw those :) but I can't really see where it's different that it matters. but today is a new day, so maybe I'll see it now :) --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]