Stas Bekman <[EMAIL PROTECTED]> wrote on 11.09.2004 04:46:43:
Sorry, it was a different problem. This should fix it. Will commit that shortly.
Index: t/apr-ext/threadmutex.t =================================================================== RCS file: /home/cvs/modperl-2.0/t/apr-ext/threadmutex.t,v retrieving revision 1.1 diff -u -r1.1 threadmutex.t --- t/apr-ext/threadmutex.t 15 Jul 2004 15:30:24 -0000 1.1 +++ t/apr-ext/threadmutex.t 11 Sep 2004 00:45:41 -0000 @@ -4,6 +4,6 @@
use TestAPRlib::threadmutex;
-plan tests => TestAPRlib::threadmutex::num_of_tests(); +plan tests => TestAPRlib::threadmutex::num_of_tests(), need_threads;
TestAPRlib::threadmutex::test();
tested this with mod perl 1.99_16. All tests successfull !
Excellent.
I only had to increase APACHE_TEST_STARTUP_TIMEOUT in order to run ModPerl-Registry tests. On my machine we had to wait for 267 seconds for apache to start in ModPerl-Registry tests.
Really? How long does it take to start the main test suite? Any idea why does it take so long? Or is that that slow machine that you gave me the access to a few months ago?
-- __________________________________________________________________ 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
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
