When logging, there is no such thing as overkill. That's why god gave us grep. The full, verbose output of the build log and of the tests is indispensable. Possibly, as dmake has just seen a new version, the version number of $Config{make} could be of interest too, especially as your focus is on non-MS Win32 Perl distributions.

I thinkt that MSVC also uses $ENV{INCLUDE} and $ENV{LIB} to indicate the include and library directories.

One thing of possible other interest could be the number of CPUs the machine has, just to track down potential race condition problems causing tests to fail - on Win32, this would be via $ENV{NUMBER_OF_PROCESSORS}, at least on Windows 2000 onwards.

In reply to Re: What should be captured in automated test reports? by Corion
in thread What should be captured in automated test reports? by xdg

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.