On Mon, Nov 05, 2012 at 04:54:00PM +0900, Shmuel Fomberg wrote: > Can anyone tell me, when a cpan smoker / tester is trying to test a module > but fails to install a dependency, what happens?
The report will be discarded. > Who should I convince to make such a failure similar to test fail? No-one, because it's not a test failure, it's a missing pre-requisite. > Or maybe mark it as failure to all the modules that depend on the failed > module? The failure may not matter to everyone though - it might only affect people on a particular platform, or a particular version of perl, or who use a particular version of a proprietary library, or who use a particular compiler. > I seek to do it because lately modules feel free to have deep dependencies, > a lot of modules have some small test failure percentage, and these add up > rather quickly. > > It is annoying to try and installed some new-shiny module, just to see some > dep^3 fails testing, and then to start investigating. This is why <http://deps.cpantesters.org/> and <http://analysis.cpantesters.org/> exist. -- David Cantrell | http://www.cantrell.org.uk/david Longum iter est per praecepta, breve et efficax per exempla.
