in reply to Test Failure Best Practices, or when is it ok to "force install"
Test failures are an indicator of either a bug or a problem with your system. In most cases, the latter should also be classified as a bug, unless the module author has documented that it should not, or is not intended to work on platform X.
As a first port of call, check the README or INSTALL. Just to make sure that this is a normal CPAN install.
Secondly, check CPAN testers to see what install problems, if any, have been encountered by the smoke testers. This is linked from the search.cpan.org module page.
Finally, check RT (also linked from the same place) to see if anyone else has reported this problem. If this is not the case, report the problem yourself to RT, which will result in the module author getting an email, and you have a ticket number that you can use to track progress.
As to whether to proceed installing a module with failing tests, "Caveat updator"; on your conscience be it. If you can work out what the tests/module _should_ be doing, stick a patch into the RT ticket; the author will in most cases be grateful.
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Test Failure Best Practices, or when is it ok to "force install"
by exussum0 (Vicar) on Jun 26, 2006 at 20:25 UTC | |
by rinceWind (Monsignor) on Jun 27, 2006 at 07:01 UTC |