Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the CPAN-Reporter CPAN distribution.

Report information
The Basics
Id: 21566
Status: resolved
Priority: 0/
Queue: CPAN-Reporter
People
Owner: dagolden [...] cpan.org
Requestors: ANDK [...] cpan.org
SZABGAB [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: 0.17
Fixed in: (no value)

History Show all quoted text
  Tue Sep 19 02:16:21 2006 ANDK [...] cpan.org - Ticket created
Subject: What to do if a module does not compile?
CPAN::Reporter is limited to test results. But if a module cannot be compiled, I currently see no convenient way to report it to the author. What's needed? Is there at least a recommendation how to proceed?
  Tue Sep 19 07:46:02 2006 david [...] hyperbolic.net - Correspondence added
Subject: Re: [rt.cpan.org #21566] What to do if a module does not compile?
Date: Tue, 19 Sep 2006 07:45:31 -0400
To: bug-CPAN-Reporter [...] rt.cpan.org
From: David Golden <david [...] hyperbolic.net>
Andreas Koenig via RT wrote: Show quoted text
> CPAN::Reporter is limited to test results. But if a module cannot be > compiled, I currently see no convenient way to report it to the author. > What's needed? Is there at least a recommendation how to proceed?
I would pose this question to CPAN Testers or Perl QA -- should it be reported "NA" (didn't work for that architecture) or should it be an extension of the current categories: PASS, FAIL, NA, UNKNOWN. Perhaps "BUILDFAIL" or something. How does YACSmoke handle it? Does it report "NA" for that architecture? We could look into doing the same.
  Tue Sep 19 07:46:05 2006 The RT System itself - Status changed from 'new' to 'open'
  Wed Sep 20 00:20:31 2006 andreas.koenig.gmwojprw [...] franz.ak.mind.de - Correspondence added
CC: ANDK [...] cpan.org
Subject: Re: [rt.cpan.org #21566] What to do if a module does not compile?
Date: Wed, 20 Sep 2006 06:20:01 +0200
To: bug-CPAN-Reporter [...] rt.cpan.org
From: andreas.koenig.gmwojprw [...] franz.ak.mind.de (Andreas J. Koenig)
Show quoted text
>>>>> On Tue, 19 Sep 2006 07:46:07 -0400, "David A. Golden via RT" <bug-CPAN-Reporter@rt.cpan.org> said:
Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=21566 >
Show quoted text
> Andreas Koenig via RT wrote:
>> CPAN::Reporter is limited to test results. But if a module cannot be >> compiled, I currently see no convenient way to report it to the author. >> What's needed? Is there at least a recommendation how to proceed?
Show quoted text
> I would pose this question to CPAN Testers or Perl QA -- should it be > reported "NA" (didn't work for that architecture) or should it be an > extension of the current categories: PASS, FAIL, NA, UNKNOWN. Perhaps > "BUILDFAIL" or something.
Show quoted text
> How does YACSmoke handle it? Does it report "NA" for that architecture? > We could look into doing the same.
I got the impression that cpan testers have no mailing list. The mailing list where every few minutes a new report comes in does not provide an environment suited for discussing protocol. Am I missing something? -- andreas
  Mon Sep 25 07:04:34 2006 SZABGAB [...] cpan.org - Ticket #21691: Ticket created
Subject: reporting early failure?
Would it be possible to add reporting on very early failures as well? E.g. while I was trying to upgrade Archive::Any I got the following. Would it be possible to send failure reports on such events as well? Gabor [...] Archive-Any-0.093/Makefile.PL Removing previously used /home/insecure/.cpan/build/Archive-Any-0.093 CPAN: Module::Build loaded ok CPAN.pm: Going to build C/CM/CMOORE/Archive-Any-0.093.tar.gz Checking if your kit is complete... Looks good Writing Makefile for Archive::Any cp lib/Archive/Any/Plugin/Zip.pm blib/lib/Archive/Any/Plugin/Zip.pm cp lib/Archive/Any/Plugin/Tar.pm blib/lib/Archive/Any/Plugin/Tar.pm cp lib/Archive/Any.pm blib/lib/Archive/Any.pm cp lib/Archive/Any/Plugin.pm blib/lib/Archive/Any/Plugin.pm Manifying blib/man3/Archive::Any::Plugin::Zip.3pm Manifying blib/man3/Archive::Any::Plugin::Tar.3pm Manifying blib/man3/Archive::Any::Plugin.3pm Manifying blib/man3/Archive::Any.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" Build.PL Build Too early to specify a build action 'Build'. Do 'Build Build' instead. make: *** [Build] Error 2 /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install make had returned bad status, install seems impossible Failed during this command: CMOORE/Archive-Any-0.093.tar.gz : make NO
  Mon Sep 25 07:44:31 2006 dagolden [...] cpan.org - Ticket #21691: Correspondence added
RT-Send-CC: andk [...] cpan.org
On Mon Sep 25 07:04:34 2006, SZABGAB wrote: Show quoted text
> Would it be possible to add reporting on very early failures as well? > E.g. while I was trying to upgrade Archive::Any I got the following. > Would it be possible to send failure reports on such events as well?
Show quoted text
> make: *** [Build] Error 2 > /usr/bin/make -- NOT OK > Running make test > Can't test without successful make > Running make install > make had returned bad status, install seems impossible > Failed during this command: > CMOORE/Archive-Any-0.093.tar.gz : make NO >
This is similar to "#21566: What to do if a module does not compile?" There's a logic issue in what to report -- it's not clear if this is in the mandate of CPAN Testers. It seems like an "NA" result, to me. Seeing this output made it clearer to me what the issues are. Right now, CPAN.pm doesn't get to the point of running tests if make/Build fails. So there would need to be some bigger surgery. It might mean that CPAN::Reporter just adds a make() reporting function and it gets integrated to CPAN the same way as it does for test. I'll take it up with Andreas.
  Mon Sep 25 07:44:31 2006 The RT System itself - Ticket #21691: Status changed from 'new' to 'open'
  Mon Sep 25 09:40:08 2006 SZABGAB [...] cpan.org - Ticket #21691: Correspondence added
Subject: Re: [rt.cpan.org #21691] reporting early failure?
Date: Mon, 25 Sep 2006 16:39:51 +0300
To: bug-CPAN-Reporter [...] rt.cpan.org
From: "Gabor Szabo" <SZABGAB [...] cpan.org>
On 9/25/06, via RT <bug-CPAN-Reporter@rt.cpan.org> wrote: Show quoted text
> This is similar to "#21566: What to do if a module does not compile?" > There's a logic issue in what to report -- it's not clear if this is in > the mandate of CPAN Testers. It seems like an "NA" result, to me.
I think such issues should be also coordinated with the rest of the people involved in the CPAN Testers effort like Barbie. Maybe on the perl-qa list. Gabor
  Sat Feb 10 22:38:01 2007 dagolden [...] cpan.org - Ticket #21691: Taken
  Sat Feb 10 22:39:41 2007 dagolden [...] cpan.org - Taken
  Fri Jul 27 00:26:50 2007 dagolden [...] cpan.org - Ticket #21691: Merged into ticket #21566
  Fri Jul 27 00:26:53 2007 dagolden [...] cpan.org - Merged into ticket #21566
  Fri Jul 27 00:29:17 2007 dagolden [...] cpan.org - Correspondence added
As per CPAN Testers, Makefile.PL/Build.PL and make/Build failures should be reported as 'FAIL'. Necessary functionality has been added to CPAN::Reporter in the repository trunk and work is underway to integrate this into CPAN.pm.
  Sun Aug 12 17:17:59 2007 dagolden [...] cpan.org - Correspondence added
This capability has been added to the latest dev releases of CPAN and CPAN::Reporter.
  Sun Aug 12 17:18:01 2007 dagolden [...] cpan.org - Status changed from 'open' to 'resolved'