manchot has asked for the wisdom of the Perl Monks concerning the following question:

I've just tried to update my Apache::AuthCookie via -MCPAN.
No complaints till I get to the test phase,
when it fails 13/17 tests.

My problem is, I have no idea what's failing, so no idea what to do about it..

Failed Test Stat Wstat Total Fail Failed List of Failed ---------------------------------------------------------- t/real.t 17 13 76.47% 3-9 11-14 16-17

It seems the only tests that pass are those that are supposed to fail...

Specs: perl 5.6.1 on RH7.1-ish linux / Apache 1.3.27

thanks,
- manchot

Replies are listed 'Best First'.
Re: CPAN Apache::AuthCookie fails test
by bbfu (Curate) on May 03, 2003 at 18:57 UTC

    I would recommend that you read the test scripts and determine exactly why they're failing. Only when you understand that, and know whether they're failing for valid reasons or not, should you force the install.

    I don't know why that particular module's tests might be failing (I don't have Apache installed, so I can't check), but it could well be failing for a good reason. OTOH, I've had at least one module (Net::Server, specifically) that failed a test for no good reason (I was installing it on win32 and the tests used alarm though none of the module code actually relied on alarm), and forcing the install allowed the module to work fine.

    The tests are there for a reason, and you shouldn't just blindly ignore them when they're reporting a problem. :)

    Update: Once you've started / tried to install the module, the tests scripts are located in your CPAN build directory, usually ~/.cpan/build/<module filename>/t/

    bbfu
    Black flowers blossom
    Fearless on my breath

Re: CPAN Apache::AuthCookie fails test
by jgallagher (Pilgrim) on May 03, 2003 at 16:53 UTC
    This may be a really bad habit, but when that happens, I tend to force install Module::Name and just ignore the failed tests. It hasn't come back to bite me yet...

          Thanks, folks. Guess I'll try forcing it ... :-/
          And maybe contacting the author of the module, too..
          anybody else encountered this kind of thing?

          - manchot