Re: Test Failure Best Practices, or when is it ok to "force install"

Test failures are to be expected. Ideally, we would like to be able to install a module with no problems. That hasn't been my experience. I'd say %50 of the modules that I have installed have been problematic. The suggestions in the other replies are great--Read the Readme, Install, etc. pods. Debug, rerun the tests, but, for me, I always go back to the Makefile.PL and tinker with it until it looks right to me. Then install the module with make -ik, make -ikt; make test -ik, make test -ikt; make install -ik, make install -ikt. Sometimes I rerun make as: "make -B", then start the procedure all over again. I wish there was an easier way(smile)...

Comment on Re: Test Failure Best Practices, or when is it ok to "force install"

Replies are listed 'Best First'.
Re^2: Test Failure Best Practices, or when is it ok to "force install" by adrianh (Chancellor) on Jun 27, 2006 at 09:36 UTC
Test failures are to be expected That's not been my experience - on a wide variety of systems (with the exception of Windows which I rarely use so can't really comment on). However I have wasted huge amounts of time debugging problems on other peoples systems where modules have been installed with failing tests because, surprisingly enough, the failing tests usually demonstrate that the module isn't working properly. Please. For the sanity of the maintainers. Don't install modules with failing tests unless you understand why they're failing :-)	[reply]

Replies are listed 'Best First'.

Re^2: Test Failure Best Practices, or when is it ok to "force install"
by adrianh (Chancellor) on Jun 27, 2006 at 09:36 UTC

Test failures are to be expected

That's not been my experience - on a wide variety of systems (with the exception of Windows which I rarely use so can't really comment on).

However I have wasted huge amounts of time debugging problems on other peoples systems where modules have been installed with failing tests because, surprisingly enough, the failing tests usually demonstrate that the module isn't working properly.

Please. For the sanity of the maintainers. Don't install modules with failing tests unless you understand why they're failing :-)

[reply]