Hi,
you might have a look at Unix::Statgrab - here
(http://cpantesters.org/cpan/report/0862c396-36c4-11e4-94e8-f232e0bfc7aa) is an
example output of a failing Makefile.PL which causes UNKNOWN test results
instead of fail.
General hint: be more verbose - on STDERR and let Makefile.PL fail when
To minimize the amount of data that has to be transmitted and stored, only
output from the last step to run is generally sent. So asking the tester
or adding .t files that dump diagnostic data are generally the best options.
David
On Mon, Dec 8, 2014 at 3:14 AM, sisyph...@optusnet.com.au
Dying Makefile.PL is the last step :)
The referred example failed to loading the XS result without any information
what failed.
A compiler or linker error would lead to broken make stage with output - so
it's likely recommended to improve the tests (eg. by using C::AC ^^).
In doubt (no answer
In doubt (no answer from a tester), one can easily add a test showing
config.log on fail of module load ...
Where can this file be found? I'll happily write a Dist::Zilla plugin that
adds such a test, and add it to all XS-based distributions I help maintain,
if I know what the test should look
I've used Config::AutoConf a bit and I think it saves results to a file.
For your hand-rolled config test, after each one, you could just save the
$out variable to files with different names and then have a .t file read
them and dump them with diag().
David
On Mon, Dec 8, 2014 at 7:05 PM,
