Skip Menu |

This queue is for tickets about the Smolder CPAN distribution.

Report information
The Basics
Id: 52072
Status: resolved
Priority: 0/
Queue: Smolder

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

Bug Information
Severity: Critical
Broken in: 1.40
Fixed in: (no value)



Subject: crashes when uploading smoke report
This is after a successful smolder install with it's unit tests passing. Any idea how to fix this? Could you give me a patch/instructions ahead of a release? I'm really eager to get this up and running :) [Dispatch] ERROR for request '/app/developer_projects/process_add_report/1': Error executing run mode 'process_add_report': Can't call method "tests_planned" on an undefined value at /usr/local/share/perl/5.10.0/Smolder/DB/SmokeReport.pm line 511. at /usr/local/share/perl/5.10.0/CGI/Application/Dispatch.pm line 704
What versions of TAP::Harness and TAP::Harness::Archive do you have installed?
On Wed Nov 25 16:22:10 2009, WONKO wrote: Show quoted text
> What versions of TAP::Harness and TAP::Harness::Archive do you have > installed?
That was it! libtest-harness-perl (debian package) was installed - for some reason it's TAP::Harness was being picked up ahead of the CPAN one. What's really strange about that is that all of the unit tests passed. I'm guessing in that stage, the PERL5INC had been modified. I guess it's still a bug that the tests are allowed to pass when the code wont work in production, but I'm not sure if that's an error with you, Module::Build, or CPAN. Definately a weridness that Module::Build will install packages in a place where debian can't find them correctly. The old one was in /usr/share/perl5, and the new one was in /usr/share/perl/5.10.0 -- once I removed the old one, all is well. Do you think that's a bug with debian or MB?
On Wed Nov 25 16:39:50 2009, CRAKRJACK wrote: Show quoted text
> libtest-harness-perl (debian package) was installed - for some reason > it's TAP::Harness was being picked up ahead of the CPAN one. > > What's really strange about that is that all of the unit tests passed.
Do you know if they were all run? Maybe there was a strange condition that caused them to be skipped but still look like a pass? Just a wild guess there though. Show quoted text
> I'm guessing in that stage, the PERL5INC had been modified. I guess it's > still a bug that the tests are allowed to pass when the code wont work > in production, but I'm not sure if that's an error with you, > Module::Build, or CPAN.
Yeah, that's a weird one. I would think it would be installed in the right place before Smolder runs without having to rely on @INC to point to build directories. Show quoted text
> Definately a weridness that Module::Build will install packages in a > place where debian can't find them correctly.
Or it's installing them in a place that comes later than what Debian has for it's own version. Show quoted text
> The old one was in > /usr/share/perl5, and the new one was in /usr/share/perl/5.10.0 -- once > I removed the old one, all is well. Do you think that's a bug with > debian or MB?
Good question. It might actually be a problem with the CPAN shell by providing a PERL5INC that won't be the same when the program is run by itself. Although that would have just caused Smolder to not install at all and you'd still have to track down why Debian wasn't seeing the newest version of Test::Harness. Going to resolve this though since it's not my bug :)