Are you sure this is because of this last change? I haven't really changed much. If you revert it, does it work ok?
no, it wasn't due to the last change in echo_timeout.pm - I was just searching for the most recent change to respond to :)
but it is something fairly recent - my nightly builds just started hanging and they weren't last week (though I don't know exactly when the hanging started).
2.0 tests just fine, so if there isn't time to track down the difference between 2.0 and 2.1 we could just skip the test for the moment, and reactivate it when you get the time to examine the differing APIs (or whatever it is).
Could you try using cvs -D to checkout older versions to find the right change? A binary search should find that pretty quickly. You want the whole thing and not only the tests, since it could be the change in the C code.
e.g.: % cvs co -D 20040601 -d mp2-20040601 modperl-2.0
-- __________________________________________________________________ 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]
