Now these tests suites won't be normally run by users ('make test'), but could be invoked via 'make alltests' or alike if they want to (or if they report a problem that is tested by one of these suites. We, developers, can always run those as part of the routine smoke.
I'll give you an interesting example for the first candidate. If you register a cleanup handler and it happens to be run in the very last request and it takes some time for it to finish, if 'apachectl stop' is run while it's still running apr's pool handler will segfault (I think not a mp problem, but didn't debug enough to tell for sure). Since on different machines timing could be very different, I'd like this cleanup handler to do 'sleep 20' or even more to make sure that 'apachectl stop' for sure needs to wait for this cleanup handler to finish. I don't think we can fit this test into the main test suite.
Another test suite is needed to test how we operate with 'PerlOptions +Autoload' which if just committed a fix for, since the problem wasn't revealed until I manually added it trying to debug some other problem (it was due to PerlSetFilter not being a real perl handler). We can't put it into the main test suite as it'll cause some of the important tests to be missed.
You can probably come up with other good examples.
__________________________________________________________________ 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]
