Hey, Perrin, When I say that Test::Builder/Test::More/etc. are tightly coupled, I'm talking really entwined. In some cases, we have created a class with a bunch of test-related methods that look through the symbol table and find methods that =~ m/^test_/ and then we run those tests, which include calls to Test::Builder methods. There's no easy way to turn this off.
When you say that we could load it conditionally -- again, not really an option -- are you thinking that we could do a conditional require() and import explicitly or use fully-qualified calls? Eric > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Perrin Harkins > Sent: Thursday, September 04, 2008 6:36 PM > To: Berg, Eric > Cc: modperl@perl.apache.org > Subject: Re: mod_perl2 + ModPerl::RegistryPrefork + > Test::Builder = segfault > > On Thu, Sep 4, 2008 at 6:09 PM, Berg, Eric > <[EMAIL PROTECTED]> wrote: > > Many of our core modules contain test methods that are > executed during > > our CVS checkin process as regression tests, so we'd have > to completely > > redo our regression testing architecture to decouple > Test::Builder from > > our code. > > As a quick fix, you could load it conditionally based on whether or > not $ENV{MOD_PERL} is true. > > - Perrin > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. -------- IRS Circular 230 Disclosure: Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.
