Last 30 days

• Nov 30, 2009

  issue 21 (test dep missing) reported by lars.dieckow   -   [2009-11-30 18:16+0100] <Apocalypse@#toolchain> Aha no wonder my test reports are failing, Test::Reporter doesn't list LWP::UserAgent as a dependency ( needed for Test::Reporter::HTTPGateway )

  [2009-11-30 18:16+0100] <Apocalypse@#toolchain> Aha no wonder my test reports are failing, Test::Reporter doesn't list LWP::UserAgent as a dependency ( needed for Test::Reporter::HTTPGateway )

Earlier this year

• Oct 07, 2009

  issue 20 (Please allow the editor to be configured in C:\strawberry\pe...) reported by sgc...@internode.on.net   -   When installed in Strawberry Perl I found that the default editor is set in C:\strawberry\perl\site\lib\Test\Reporter.pm It is defaulted to Notepad. But the report files have UNIX endings and therefore looks awful and unreadable in Notepad. While I did change Reporter.pm to spawn my editor of choice (Notepad++), I would have preferred to have been able to make that config change in C:\strawberry\perl\lib\CPAN\Config.pm and/on been able to make that change with cpan> o conf init test_report

  When installed in Strawberry Perl I found that the default editor is set in C:\strawberry\perl\site\lib\Test\Reporter.pm It is defaulted to Notepad. But the report files have UNIX endings and therefore looks awful and unreadable in Notepad. While I did change Reporter.pm to spawn my editor of choice (Notepad++), I would have preferred to have been able to make that config change in C:\strawberry\perl\lib\CPAN\Config.pm and/on been able to make that change with cpan> o conf init test_report
• Apr 07, 2009

  issue 17 (Don't send reports for LOCAL author id) Labels changed by xdaveg   -   probably won't be fixed here, but may be addressed in CPAN Testers 2.0

  Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium

  probably won't be fixed here, but may be addressed in CPAN Testers 2.0

  Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium
• Apr 07, 2009

  issue 16 ($editor fails to start to edit failed report and no inidcati...) Status changed by xdaveg   -   Fixed for 1.53_01 release

  Status: Fixed

  Fixed for 1.53_01 release

  Status: Fixed
• Apr 07, 2009

  issue 18 (reply-to cpan-testers-discuss) Status changed by xdaveg   -   As cpan-testers is moving away from email, this feature will not be added.

  Status: WontFix

  As cpan-testers is moving away from email, this feature will not be added.

  Status: WontFix

Older

• Nov 03, 2008

  issue 19 (-x Mail::Send does not work) Status changed by xdaveg   -   Thanks. Applied patch and released as Test::Reporter 1.5202

  Status: Fixed

  Thanks. Applied patch and released as Test::Reporter 1.5202

  Status: Fixed
• Nov 03, 2008

  issue 19 (-x Mail::Send does not work) commented on by moshe.kamensky   -   I attach a patch

  I attach a patch
• Oct 30, 2008

  issue 19 (-x Mail::Send does not work) commented on by esert...@yahoo.de   -   Additionally, the mail fragment is saved to ~/dead.letter. But it seems that at least the CC: field looks wrong: From cpansand Thu Oct 30 21:11:28 2008 Return-Path: <cpansand> Received: (from cpansand@localhost) by biokovo.herceg.de (8.13.6/8.13.6/Submit) id m9UKBS7V084879; Thu, 30 Oct 2008 21:11:28 +0100 (CET) (envelope-from cpansand) Date: Thu, 30 Oct 2008 21:11:28 +0100 (CET) Message-Id: <200810302011.m9UKBS7V084879@biokovo.herceg.de> Subject: FAIL WWW-Mechanize-1.50 i386-freebsd 6.1-release From: srezic@cpan.org To: cpan-testers@perl.org Cc: ARRAY (0x83cfe44) X-Reported-Via: Test::Reporter 1.5201, via cpantest 1.5201 Regards, Slaven

  Additionally, the mail fragment is saved to ~/dead.letter. But it seems that at least the CC: field looks wrong: From cpansand Thu Oct 30 21:11:28 2008 Return-Path: <cpansand> Received: (from cpansand@localhost) by biokovo.herceg.de (8.13.6/8.13.6/Submit) id m9UKBS7V084879; Thu, 30 Oct 2008 21:11:28 +0100 (CET) (envelope-from cpansand) Date: Thu, 30 Oct 2008 21:11:28 +0100 (CET) Message-Id: <200810302011.m9UKBS7V084879@biokovo.herceg.de> Subject: FAIL WWW-Mechanize-1.50 i386-freebsd 6.1-release From: srezic@cpan.org To: cpan-testers@perl.org Cc: ARRAY (0x83cfe44) X-Reported-Via: Test::Reporter 1.5201, via cpantest 1.5201 Regards, Slaven
• Oct 30, 2008

  issue 19 (-x Mail::Send does not work) reported by esert...@yahoo.de   -   If trying the Mail::Send backend, then I get the following error /usr/perl5.6.2/-g fail -from "srezic@cpan.org" -t "t/local/back.t test kills CPAN.pm" -p WWW-Mechanize-1.50 -x Mail::Send ... Test::Reporter: error from 'Test::Reporter::Transport::Mail::Send:' Can't locate object method "report" via package "Test::Reporter::Transport::Mail::Send" (perhaps you forgot to load "Test::Reporter::Transport::Mail::Send"?) at /usr/perl5.6.2/lib/site_perl/5.6.2/Test/Reporter/Transport/Mail/Send.pm line 40, <STDIN> line 2. This is with: $ /usr/perl5.6.2/bin/perl -MTest::Reporter\ 9999 Test::Reporter version 9999 required--this is only version 1.5201.

  If trying the Mail::Send backend, then I get the following error /usr/perl5.6.2/-g fail -from "srezic@cpan.org" -t "t/local/back.t test kills CPAN.pm" -p WWW-Mechanize-1.50 -x Mail::Send ... Test::Reporter: error from 'Test::Reporter::Transport::Mail::Send:' Can't locate object method "report" via package "Test::Reporter::Transport::Mail::Send" (perhaps you forgot to load "Test::Reporter::Transport::Mail::Send"?) at /usr/perl5.6.2/lib/site_perl/5.6.2/Test/Reporter/Transport/Mail/Send.pm line 40, <STDIN> line 2. This is with: $ /usr/perl5.6.2/bin/perl -MTest::Reporter\ 9999 Test::Reporter version 9999 required--this is only version 1.5201.
• Oct 11, 2008

  issue 18 (reply-to cpan-testers-discuss) reported by xdaveg   -   Both in the email and in a reply-to header, direct replies to cpan-testers-discuss

  Both in the email and in a reply-to header, direct replies to cpan-testers-discuss
• Oct 08, 2008

  issue 17 (Don't send reports for LOCAL author id) reported by xdaveg   -   Some people inject CPAN distributions into a local CPAN mirror under the LOCAL username. Test reports should not be sent for such distributions.

  Some people inject CPAN distributions into a local CPAN mirror under the LOCAL username. Test reports should not be sent for such distributions.
• Oct 01, 2008

  issue 16 ($editor fails to start to edit failed report and no inidcati...) commented on by martin.j.evans   -   config.ini: edit_report=default:ask/yes pass/na:no email_from=xxx@yyy.com send_report=default:ask/yes pass/na:yes smtp_server=smtp.yyy.local "It's very odd that Test::Reporter would think that 'CPAN::Reporter::Smoker' is an editor." Yes, I somehow did not notice that and just thought something had stopped vi launching. Can't see how it would harm to stick the $Report or $! in all the same. Since this happened vi starts fine so I cannot currently reproduce it but I'll try.

  config.ini: edit_report=default:ask/yes pass/na:no email_from=xxx@yyy.com send_report=default:ask/yes pass/na:yes smtp_server=smtp.yyy.local "It's very odd that Test::Reporter would think that 'CPAN::Reporter::Smoker' is an editor." Yes, I somehow did not notice that and just thought something had stopped vi launching. Can't see how it would harm to stick the $Report or $! in all the same. Since this happened vi starts fine so I cannot currently reproduce it but I'll try.
• Sep 30, 2008

  issue 16 ($editor fails to start to edit failed report and no inidcati...) commented on by xdaveg   -   It's very odd that Test::Reporter would think that 'CPAN::Reporter::Smoker' is an editor. Please send/attach your .cpanreporter/config.ini. You can replace your email address with 'johndoe@example.com' to keep it private. Thanks, David

  It's very odd that Test::Reporter would think that 'CPAN::Reporter::Smoker' is an editor. Please send/attach your .cpanreporter/config.ini. You can replace your email address with 'johndoe@example.com' to keep it private. Thanks, David
• Sep 30, 2008

  issue 16 ($editor fails to start to edit failed report and no inidcati...) reported by martin.j.evans   -   What steps will reproduce the problem? I'm not sure but I have my CPAN::Reporter::Smoker set to ask to edit error reports before sending them. Yesterday I may have ctrl/c'ed (intr) in one of those vi sessions (because I was about to send a report that was not a module failure but a command line too lone) and today when I restarted my smoker and it reached a failure I got the vi prompt with default "yes" but it did not start. What is the expected output? What do you see instead? vi starts and I edit the report Test::Reporter: The editor `CPAN::Reporter::Smoker' could not be run at / home/martin/perl10/lib/site_perl/5.10.0/Test/Reporter.pm line 549, <STDIN> line 1. What version of the product are you using? On what operating system? 1.5201 on Linux with perl 5.10.0. Please provide any additional information below. Can I politely suggest you change line 549 in Reporter.pm to: die __PACKAGE__, ": The editor `$editor' could not be run on $Report - $!" if system "$editor $Report"; then I might be able to tell why vi failed. i.e., add the report name and $! for the system error. It may alos be useful to stop and require some sort of acknowledgement because I only just noticed this and had to ctrl/s and scroll back to what had happened.

  What steps will reproduce the problem? I'm not sure but I have my CPAN::Reporter::Smoker set to ask to edit error reports before sending them. Yesterday I may have ctrl/c'ed (intr) in one of those vi sessions (because I was about to send a report that was not a module failure but a command line too lone) and today when I restarted my smoker and it reached a failure I got the vi prompt with default "yes" but it did not start. What is the expected output? What do you see instead? vi starts and I edit the report Test::Reporter: The editor `CPAN::Reporter::Smoker' could not be run at / home/martin/perl10/lib/site_perl/5.10.0/Test/Reporter.pm line 549, <STDIN> line 1. What version of the product are you using? On what operating system? 1.5201 on Linux with perl 5.10.0. Please provide any additional information below. Can I politely suggest you change line 549 in Reporter.pm to: die __PACKAGE__, ": The editor `$editor' could not be run on $Report - $!" if system "$editor $Report"; then I might be able to tell why vi failed. i.e., add the report name and $! for the system error. It may alos be useful to stop and require some sort of acknowledgement because I only just noticed this and had to ctrl/s and scroll back to what had happened.
• Sep 08, 2008

  issue 13 (new() in Test::Reporter Pod ) Status changed by xdaveg   -   Fixed in 1.52

  Status: Fixed

  Fixed in 1.52

  Status: Fixed
• Sep 08, 2008

  issue 14 (subject member has an extra newline) Status changed by xdaveg   -   This was a bug in parsing of saved reports. Fixed in the repo and will be released soon.

  Status: Fixed

  This was a bug in parsing of saved reports. Fixed in the repo and will be released soon.

  Status: Fixed
• Sep 07, 2008

  issue 15 ([PATCH] Resolving maildomain is very very very slow) Status changed by xdaveg   -   Thanks. Applied, tweaked and released as 1.51_02

  Status: Fixed

  Thanks. Applied, tweaked and released as 1.51_02

  Status: Fixed
• Sep 07, 2008

  issue 15 ([PATCH] Resolving maildomain is very very very slow) reported by jos.i.boumans   -   Im using T::R 1.51_01 on perl 5.8.8. On my machine, resolving the ->from address ends up calling Net::SMTP->new for a few mailhosts to determine my maildomain. Since the timeout per call is 120 seconds, this is a very lengthy process. The attached patch does a few things: 1) It caches the result of the ->_maildomain() call 2) It lowers the timeout for Net::SMTP->new from 120 seconds to 5 seconds 3) It adds the host 'smtp' to check for a maildomain 4) 1.51_01 does not return a 'true' value at the end of file (there's an __END__ marker before the end) For clarity, I've omitted whitespace changes (since this does a block indent). You may want to add that yourself to suit your coding style. $ diff -dwu lib/Test//Reporter.pm.org lib/Test/Reporter.pm --- lib/Test//Reporter.pm.org 2008-09-07 15:02:01.000000000 +0200 +++ lib/Test/Reporter.pm 2008-09-07 15:35:25.000000000 +0200 @@ -563,11 +563,15 @@ } # From Mail::Util 1.74 (c) 1995-2001 Graham Barr (c) 2002-2005 Mark Overmeer +{ # cache the result of this, so we don't try to resolve this *every* + # iteration -kane + my $domain; + sub _maildomain { my $self = shift; warn __PACKAGE__, ": _maildomain\n" if $self->debug(); - my $domain = $ENV{MAILDOMAIN}; + $domain = $ENV{MAILDOMAIN} if defined $ENV{MAILDOMAIN}; return $domain if defined $domain; @@ -616,8 +620,12 @@ if (eval {require Net::SMTP}) { my $host; - for $host (qw(mailhost localhost)) { - my $smtp = eval {Net::SMTP->new($host)}; + for $host (qw(mailhost smtp localhost)) { + + # default timeout is 120, which is Very Very Long, so lower + # it to 5 seconds. Total slowdown will not be more than + # 15 seconds ( 5 x @hosts ) --kane + my $smtp = eval {Net::SMTP->new($host, Timeout => 5)}; if (defined $smtp) { $domain = $smtp->domain; @@ -643,6 +651,7 @@ return $domain; } +} # From Mail::Util 1.74 (c) 1995-2001 Graham Barr (c) 2002-2005 Mark Overmeer sub _mailaddress { @@ -689,6 +698,9 @@ return $perl =~ /^perl-?\d\.\d/; } +# need a true value +1; + __END__ =head1 NAME

  Im using T::R 1.51_01 on perl 5.8.8. On my machine, resolving the ->from address ends up calling Net::SMTP->new for a few mailhosts to determine my maildomain. Since the timeout per call is 120 seconds, this is a very lengthy process. The attached patch does a few things: 1) It caches the result of the ->_maildomain() call 2) It lowers the timeout for Net::SMTP->new from 120 seconds to 5 seconds 3) It adds the host 'smtp' to check for a maildomain 4) 1.51_01 does not return a 'true' value at the end of file (there's an __END__ marker before the end) For clarity, I've omitted whitespace changes (since this does a block indent). You may want to add that yourself to suit your coding style. $ diff -dwu lib/Test//Reporter.pm.org lib/Test/Reporter.pm --- lib/Test//Reporter.pm.org 2008-09-07 15:02:01.000000000 +0200 +++ lib/Test/Reporter.pm 2008-09-07 15:35:25.000000000 +0200 @@ -563,11 +563,15 @@ } # From Mail::Util 1.74 (c) 1995-2001 Graham Barr (c) 2002-2005 Mark Overmeer +{ # cache the result of this, so we don't try to resolve this *every* + # iteration -kane + my $domain; + sub _maildomain { my $self = shift; warn __PACKAGE__, ": _maildomain\n" if $self->debug(); - my $domain = $ENV{MAILDOMAIN}; + $domain = $ENV{MAILDOMAIN} if defined $ENV{MAILDOMAIN}; return $domain if defined $domain; @@ -616,8 +620,12 @@ if (eval {require Net::SMTP}) { my $host; - for $host (qw(mailhost localhost)) { - my $smtp = eval {Net::SMTP->new($host)}; + for $host (qw(mailhost smtp localhost)) { + + # default timeout is 120, which is Very Very Long, so lower + # it to 5 seconds. Total slowdown will not be more than + # 15 seconds ( 5 x @hosts ) --kane + my $smtp = eval {Net::SMTP->new($host, Timeout => 5)}; if (defined $smtp) { $domain = $smtp->domain; @@ -643,6 +651,7 @@ return $domain; } +} # From Mail::Util 1.74 (c) 1995-2001 Graham Barr (c) 2002-2005 Mark Overmeer sub _mailaddress { @@ -689,6 +698,9 @@ return $perl =~ /^perl-?\d\.\d/; } +# need a true value +1; + __END__ =head1 NAME
• Aug 09, 2008

  issue 14 (subject member has an extra newline) reported by esert...@yahoo.de   -   When reading a test report previously created with the latest stable version of CPAN::Reporter (sample attached), then the subject member seems to have an extra newline: $ perl -MTest::Reporter -e 'warn "<",Test::Reporter->new->read(shift)->subject,">"' pass.Kwalify-1.18.cygwin-thread-multi-64int.1.5.24\(0.15642\).1218228801.2440.rpt <PASS Kwalify-1.18 cygwin-thread-multi-64int 1.5.24(0.15642) > at -e line 1. This is problematic when sending this report with Net::SMTP, because the extra newline signals the end of mail headers and starts the mail body. My current workaround is to just remove the newline before sending the report: $report->{_subject} =~ s{\n}{}g; Regards, Slaven

  When reading a test report previously created with the latest stable version of CPAN::Reporter (sample attached), then the subject member seems to have an extra newline: $ perl -MTest::Reporter -e 'warn "<",Test::Reporter->new->read(shift)->subject,">"' pass.Kwalify-1.18.cygwin-thread-multi-64int.1.5.24\(0.15642\).1218228801.2440.rpt <PASS Kwalify-1.18 cygwin-thread-multi-64int 1.5.24(0.15642) > at -e line 1. This is problematic when sending this report with Net::SMTP, because the extra newline signals the end of mail headers and starts the mail body. My current workaround is to just remove the newline before sending the report: $report->{_subject} =~ s{\n}{}g; Regards, Slaven
• Aug 07, 2008

  issue 13 (new() in Test::Reporter Pod ) reported by esert...@yahoo.de   -   The documentation for the new() constructor in the Test::Reporter Pod does not mention transport_args, but it seems that it can be used, at least it is listed in _process_params. Regards, Slaven

  The documentation for the new() constructor in the Test::Reporter Pod does not mention transport_args, but it seems that it can be used, at least it is listed in _process_params. Regards, Slaven