Steve Hay wrote:
you mean re-enable t/perl/ithreads.t, skip api.t and run:
% t/TEST t/modules/reload.t t/perl/api.t t/perl/ithreads.t
just did that, and see no problem.
Yes. But how did you skip api.t? I meant edit t/response/TestPerl/api.pm so that some condition is not met in the test plan so that the chunk of code above gets run. The test plan is expressed as:
plan $r, tests => 2, need { "getppid() is not implemented on Win32" => !Apache::Build::WIN32(), "getppid() is having problems with perl 5.6" => !($] < 5.008), };
so change this to make it skip for you. (As opposed to just creating a t/SKIP file, which wouldn't involve the "exit" code above.)
That's exactly what I did (not t/SKIP). Now looking at modperl_perl_exit.
-- __________________________________________________________________ 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]
