I've looked through those tests, and none seem to apply and I'm not sure how one would even go about writing a unit test for this. We haven't even been able to reproduce the problem on all systems.
I suspect the best we can do may simply be manual load tests (such as Max and I have done) showing that this patch works. If someone have a good strategy for how to approach this, I'd love to see it since I'd much prefer to have a test. I just don't know how here. Greg On 3/6/2012 4:29 PM, Fred Moyer wrote: > On Tue, Mar 6, 2012 at 11:12 AM, Salusa Secondus > <sal...@nationstates.net> wrote: >> Fred, >> >> I'll take a look at the tests when I get home to see what I can find. >> Do you know of any specific tests which deal with multi-threading or >> potential deadlocks? > Torsten, Steve H., and Gozer know that part of the code a lot better > than I do, but here's what I found which might be useful: > > $ find t -name '*thread*' | grep -v svn > t/apr/threadmutex.t > t/apr/threadrwlock.t > t/apr-ext/threadmutex.t > t/apr-ext/threadrwlock.t > t/lib/TestAPRlib/threadmutex.pm > t/lib/TestAPRlib/threadrwlock.pm > t/perl/ithreads.t > t/perl/ithreads2.t > t/perl/ithreads_args.t > t/perl/ithreads_eval.t > t/response/TestAPR/threadmutex.pm > t/response/TestAPR/threadrwlock.pm > t/response/TestPerl/ithreads.pm > t/response/TestPerl/ithreads_args.pm > t/response/TestPerl/ithreads_eval.pm --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org For additional commands, e-mail: dev-h...@perl.apache.org
