Dear brothers and sisters of the Monastery,

I need to merge a complex set of Devel::Cover databases in order to get global usage measures, and am having some difficulty. The core problem is that while results from usage of Perl module files (.pm) can be combined across multiple databases, results for multiple perl scripts (.pl) cannot. You can apparently merge databases by calling

cover database1 database2 database3 ...

In the combined results coming out of this, all the .pm files have reasonable looking coverage metrics, and one of the .pl files does as well, but all the other .pl files while they are lissted in the output table have all 'n/a' for their coverage metrics. Has anyone ever had to do this before and come up with a good solution?

Here's a little more about my situation. I have a large, highly parallel system that I'd like to compute test coverage for. This system consists of multiple perl scripts and modules. The modules are used by multiple scripts, and some scripts call other scripts as well. The scripts often run in parallel on a Condor system with several nodes (so that scripts may be running at the same time on different comptuters all sharing the same NFS filesystem). Devel::Cover seems to be the only game in town for Perl test coverage measurement tools so that's what we are using. Because different pieces of the system run in parallel and Devel::Cover is not multi-process safe -- attempting to have all processes use the same coverage database results in a corrupted database and crashing scripts -- I have to specify a separate database for every run of every script (some scripts are run multiple times during one execution of the system)

--DrWhy

"If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."

In reply to How To Merge Devel::Cover databases by DrWhy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.