Re: Can't locate object method new via package Test::Reporter
David Golden wrote: What happens if you try loading it from the command line: $ perl5.8.8 -MTest::Reporter -we '$tr = Test::Reporter-new()' Good question. Now I can see what's going wrong (though it's a pity that CPAN hid this error message. Now, any ideas how to fix this? $ perl -MTest::Reporter -we '$tr = Test::Reporter-new()' Can't ignore signal CHLD, forcing to default. Your vendor has not defined Socket macro SOCK_RAW, used at /boot/home/config/lib/perl5/5.8.8/BePC-beos/IO/Socket/INET.pm line 24 Compilation failed in require at /boot/home/config/lib/perl5/5.8.8/BePC-beos/IO/Socket.pm line 21. Compilation failed in require at /boot/home/config/lib/perl5/5.8.8/Net/SMTP.pm line 15. BEGIN failed--compilation aborted at /boot/home/config/lib/perl5/5.8.8/Net/SMTP.pm line 15. Compilation failed in require at /boot/home/config/lib/perl5/site_perl/5.8.8/Test/Reporter.pm line 27. BEGIN failed--compilation aborted at /boot/home/config/lib/perl5/site_perl/5.8.8/Test/Reporter.pm line 27. Compilation failed in require. BEGIN failed--compilation aborted. $ -Nigel
Re: Can't locate object method new via package Test::Reporter
I've found one problem, which isn't the one mentioned, but needs fixing anyway: IO::Socket gives this error on BeOS: Your vendor has not defined Socket macro AF_UNIX, used at /boot/home/config/lib/perl5/5.8.8/BePC-beos/IO/Socket/UNIX.pm line 18 The fix is in IO/Socket.pm at line 22. Old code: require IO::Socket::UNIX if ($^O ne 'epoc' $^O ne 'symbian'); New code: require IO::Socket::UNIX if ($^O ne 'epoc' $^O ne 'symbian' $^O ne 'beos'); I've raised this as bug 53837 against IO::Socket. -Nigel
Re: Can't locate object method new via package Test::Reporter
If you make that fix, does the one-liner with Test::Reporter work? David On Wed, Jan 20, 2010 at 8:23 AM, Nigel Horne n...@bandsman.co.uk wrote: I've found one problem, which isn't the one mentioned, but needs fixing anyway: IO::Socket gives this error on BeOS: Your vendor has not defined Socket macro AF_UNIX, used at /boot/home/config/lib/perl5/5.8.8/BePC-beos/IO/Socket/UNIX.pm line 18 The fix is in IO/Socket.pm at line 22. Old code: require IO::Socket::UNIX if ($^O ne 'epoc' $^O ne 'symbian'); New code: require IO::Socket::UNIX if ($^O ne 'epoc' $^O ne 'symbian' $^O ne 'beos'); I've raised this as bug 53837 against IO::Socket. -Nigel
Re: Can't locate object method new via package Test::Reporter
David Golden wrote: If you make that fix, does the one-liner with Test::Reporter work? No, as I said, it isn't the one mentioned. I'm open to ideas. -Nigel David On Wed, Jan 20, 2010 at 8:23 AM, Nigel Horne n...@bandsman.co.uk wrote: I've found one problem, which isn't the one mentioned, but needs fixing anyway: IO::Socket gives this error on BeOS: Your vendor has not defined Socket macro AF_UNIX, used at /boot/home/config/lib/perl5/5.8.8/BePC-beos/IO/Socket/UNIX.pm line 18 The fix is in IO/Socket.pm at line 22. Old code: require IO::Socket::UNIX if ($^O ne 'epoc' $^O ne 'symbian'); New code: require IO::Socket::UNIX if ($^O ne 'epoc' $^O ne 'symbian' $^O ne 'beos'); I've raised this as bug 53837 against IO::Socket. -Nigel -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, ICQ#20252325 n...@bandsman.co.uk http://www.bandsman.co.uk
Re: Can't locate object method new via package Test::Reporter
I belie I have Test::Reporter loading: $ perl -MTest::Reporter -we '$tr = Test::Reporter-new()' Can't ignore signal CHLD, forcing to default. Name main::tr used only once: possible typo at -e line 1. $ [ Thanks David for the suggestion on how to test it loads. ] To get it to load on BeOS you need to apply the fixes I've suggested for RT bugs 53837, 53838 and 53839. I suspect I'm still some way from getting a smoker on BeOS, but I am making progress. The next thing is to find out why I'm getting Unable to connect to any MX's in .../lib/perl5/site_perl/5.8.8/Test/Reporter/Transport/Net/SMTP.pm -Nigel
Re: Of the usefulness of post release smoke test results
Hi, although I greatly appreciate the provided service (cpan smoking) it has the disadvantage to give the result long after I need it which is before I release to CPAN. I would like to see the possibility to run smoke tests as part of my pre- release tests. I see no reason to release a module if it doesn't work on a specific platform or at least I'd like to list that platform as unsupported. Although most often the errors are simply found because the test smoking machines have a different setup. You can release a development version of a module to the CPAN. Smokers will pick it up and test it, but it'll be invisible to users unless they specifically request the dev version. I also believe that the smoke test platforms should be available, on a cpan/perl/smoke test related site, as virtual machines when possible. This isn't possible for some of the more interesting platforms because of licencing constraints. This would lower the demand on the smoke test infrastructure. There are VMs available for download, IE on the OsZoo site, but those differ from the official smoke boxes. The current bottleneck isn't on smoke boxes, but on the infrastructure for dealing with the reports they generate. Running smoke tests in VMs would have the added advantage to add redundancy to the smoking infrastructure. There's already plenty of redundancy for those platforms for which it would be practical to make VM images available - those being the common free x86 OSes. The ones where we only have limited coverage - eg Sparc, Alpha, MIPS, Windows, IBM - are those for which we can't make VM images available, either because of OS licencing constraints, or because there's no suitable virtualisation environment. Can we get distributable VMs for non-free OSes? Not legally. -- David Cantrell | Reality Engineer, Ministry of Information Support terrierism! Adopt a dog today!
CPAN testing on BeOS5.0
I found that Net::Cmd is also broken on BeOS, fix is RT bug 53850. -Nigel -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, ICQ#20252325 n...@bandsman.co.uk http://www.bandsman.co.uk
