Skip Menu |

This queue is for tickets about the CPANPLUS CPAN distribution.

Report information
The Basics
Id: 11405
Status: resolved
Priority: 0/
Queue: CPANPLUS

People
Owner: Nobody in particular
Requestors: MTHURN [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.051
Fixed in: (no value)



Subject: fail report contains not enough info
The emailed failure report contains the results of un-tar and the results of `make test`, but it does NOT contain the results of `make`. I strongly recommend that the report should include the result of `make`. In addition, I think that all the messages from the un-tar are NOT necessary. (That's what MANIFEST is for!) P.S. I'm running with verbose turned on, in case that makes a difference.
[MTHURN - Mon Feb 7 09:15:52 2005]: Show quoted text
> The emailed failure report contains the results of un-tar and the > results of `make test`, but it does NOT contain the results of `make`. > I strongly recommend that the report should include the result of > `make`.
Eh, it does... at least hte code tells me it does. When you report bugs, can you please provide me examples of what goes wrong, or better yet, how to reproduce this problem? Show quoted text
> In addition, I think that all the messages from the un-tar are NOT > necessary. (That's what MANIFEST is for!)
Sorry, i disagree. Errors during untarring (permissions, broken archives, etc) have more than once been the reason for test failures. Show quoted text
> P.S. I'm running with verbose turned on, in case that makes a > difference.
It shouldn't.
There is now a module on CPAN that demonstrates this bug. Fire up cpanp and try to i Devel::Fail::MakeTest The terminal session includes the `make` which looks like this: Running [/usr/local/bin/make UNINST=1]... make_all_was_successful. But the failure report does NOT contain this. -- - - Martin 'Kingpin' Thurn
[MTHURN - Mon Feb 14 12:07:02 2005]: Show quoted text
> There is now a module on CPAN that demonstrates this bug. Fire up > cpanp and try to i Devel::Fail::MakeTest > The terminal session includes the `make` which looks like this: > > Running [/usr/local/bin/make UNINST=1]... > make_all_was_successful. > > But the failure report does NOT contain this.
Thanks for creating a handy test case; so far, only errors from the shelled out commands were collected on the stack, but now all messages are collected, including the ones that exit ok... it now looks some thing like this (as from change 11968): [....] [MSG] [Wed Feb 16 14:33:35 2005] Extracted 'Devel::Fail::MakeTest' to '/Users/kane/ .cpanplus/5.8.3/build/Devel-Fail-MakeTest-1.005' [MSG] [Wed Feb 16 14:33:36 2005] Writing Makefile for Devel::Fail::MakeTest [MSG] [Wed Feb 16 14:33:36 2005] make_all_was_successful. [ERROR] [Wed Feb 16 14:33:37 2005] MAKE TEST failed: No such file or directory PERL_DL_NONLAZY=1 /usr/local/bin/perlc "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/fail....# Failed test (t/fail.t at line 2) # Looks like you failed 1 tests of 1. dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 1 Failed 1/1 tests, 0.00% okay Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay. Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------------ - t/fail.t 1 256 1 1 100.00% 1 make: *** [test_dynamic] Error 2 [....]