When I get a failing test, I always figure out the reason for failure before doing a forced install. Even when there is only one failure of hundreds of tests, it can indicate a deeper issue, which I don't want some small problem to come back and bite me in the future. It is much easier to debug things when one has the indicator of a failure. Then, once I've figured out the reason for the problem, I'll report it to the author.

While any module with net-based tests often have failures due to changing test data, it still is important to understand why tests fail, as there can be no simple algorithm to say things are OK.

-a