On Jan 30, 2008 8:42 PM, David Golden <[EMAIL PROTECTED]> wrote: > On Jan 30, 2008 2:47 PM, Sam Tregar <[EMAIL PROTECTED]> wrote: > > > Hmm, that's a chicken-or-egg problem. If I try to check before > > WriteMakefile() then you might not have XML::SAX installed yet. You might > > be about to install a broken one, and I won't find out about that until the > > tests run. Any way to have a test fail but not get an email from CPAN > > testers? > > > > > Fails will always get reported, but you could check for a working XML::SAX > and use "plan skip_all => $reason". >
Oh well. I suppose I can setup a rule that looks for the telltale signs of a broken XML::SAX install in a fail report and just sends it to /dev/null. I'm definitely not going to make my module pass its tests when there's absolutely no way it can work! I guess that's the disconnect here - sometimes failing is good! In this case it's a clue that your setup is broken. Making that clue more explicit is a good idea, but making it go away isn't. -sam
