Nigel Horne wrote:
What is the consensus of opinion on "Trust_Test_Report_History" - are
people setting in CPAN::Config? I notice it defaults to 0, which implies
to me that the author of the program which sets the defaults doesn't
think it's a good idea, hence my caution.
From my point of view, problems that appear when setting trust_history to 1
just don't worth possible benefits.
Case 1. When you manage to make module working (and therefore pass tests), it's
not installing without force.
Example: Some module, let's name it Format::LibFormat is a prerequisite for a few hundreds modules. You run smoker, it
tries to install this module, but find out that it requires libformat library. You run "apt-get install libformat2", and
then "cpan Format::LibFormat". And it doesn't work. Previous report said it's not ok, so we're not installing it. The
same applies to modules which test suites rely on internet connectivity, as it may fail exactly when testing the module.
Case 2. You don't have any benefit for failing builds.
Example: Some module, like Super::Something fails on Perl 5.15.1, and is a prerequisite for another few hundreds
modules. It's not building because of problem with XS or something, doesn't matter. Result is UNKNOWN like in previous
case. Next time smoker tries to test/install it, it would compile it again. No benefit.
So it works only with FAIL, not UNKNOWN. And if you find a common prerequisite that is failing, it's easier to just
disable it in distroprefs.
--
Serguei Trouchelle
