Module dependencies and test results

Marvin Humphrey marvin at
Sat Aug 4 18:32:02 BST 2007

On Aug 4, 2007, at 9:17 AM, David Cantrell wrote:

> On Sat, Aug 04, 2007 at 07:19:40AM -0700, Marvin Humphrey wrote:
>> Another issue: it's fetching devel releases.  (KinoSearch 0.20_04 has
>> 6 fails out of 17; the stable release 0.15 has 3 fails out of 35.)
>> That's gonna mess things up.
> I believe that it's fetching META.yml from the latest stable  
> release of
> a module, but it needs something better for parsing test results.
> Patches welcome :-)

Mmf, I started but it's not set up to run easily on a box other than  

Since you're just screen-scraping, it looks like all you'd have to do  
is change this line to match version numbers comprised only of  
numbers and periods.

-$testresults =~ s!^(.*?)(<h2>$distname.*?</h2>).*!$2!s;
+$testresults =~ s!^(.*?)(<h2>$distname\s+\d+(?:\.\d+)*\s*?</h2>).*! 

BTW, are you familiar with Module::Depends::Tree and its deptree  
application? It works off of any CPAN mirror, including, if you  
choose, a local minicpan.  That's what I tend to use for this  
purpose.  Your service has the added bonus of showing the cpan  
testers' results, though.

Any math wizards on this list that can come up with a formula  
expressing the likelihood that an attempted installation will fail,  
based on how numerous and dubious the dependencies are?

Marvin Humphrey
Rectangular Research

More information about the mailing list