Re: Automated testing how to?
On 02/08/10 22:55, Slaven Rezic wrote: Nigel Hornen...@bandsman.co.uk writes: On 30/07/10 13:45, Chris 'BinGOs' Williams wrote: Try installing warnings::compat for 5.6 perls. Thanks for the suggestion, but that failed: cpan install warnings::compat [...] Warning: prerequisite Test::More 0 not found at (eval 1) line 219. [...] Perl 5.006 required--this is only version 5.00503, stopped at Just force install the module. But then, I don't think warnings::compat should use Test::More anymore. This is worth an RT ticket. Please clarify what you mean by the module. Do you mean Test::More or warnings::compat? Regards, Slaven -Nigel -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, ICQ#20252325, twitter: @nigelhorne n...@bandsman.co.uk http://www.bandsman.co.uk
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 09:16:04AM -0400, David Golden wrote: Personally, I see no value in testing anything before 5.6.2 and only minimal value even testing that now that 5.12 is the current production release. I was talking with someone from $networking_equipment_company last week, and they have recently switched from 5.6 to 5.8 for some of their stuff. And they use cpXXXan! I ought to get round to upgrading my 5.6.2 tester to the shiny new CT2 world, I suppose, but I have to say that it's not a particularly high priority for me. I do find it useful though (or at least I did when it was running - I turned it off when the NOC guys asked us to turn the volume down on the mailing list) if only because it caught me using a few pointless neologisms, which I find distasteful. -- David Cantrell | Reality Engineer, Ministry of Information Anyone who cannot cope with mathematics is not fully human. At best he is a tolerable subhuman who has learned to wear shoes, bathe and not make messes in the house. -- Robert A Heinlein
Re: Automated testing how to?
Nigel Horne n...@bandsman.co.uk writes: On 30/07/10 13:45, Chris 'BinGOs' Williams wrote: Try installing warnings::compat for 5.6 perls. Thanks for the suggestion, but that failed: cpan install warnings::compat [...] Warning: prerequisite Test::More 0 not found at (eval 1) line 219. [...] Perl 5.006 required--this is only version 5.00503, stopped at Just force install the module. But then, I don't think warnings::compat should use Test::More anymore. This is worth an RT ticket. Regards, Slaven -- Slaven Rezic - slaven at rezic dot de tktimex - time recording tool http://sourceforge.net/projects/ptktools/
Re: Automated testing how to?
Now I'm curious! I'll know shortly if perl 5.6.2 will compile on my OpenBSD smoker box. In any case, I can only say that I'm afraid to know why you're worried about perl-5.6.2. Why not require a newer Perl for your modules? perl 5.6 is dead, long live Perl! Jeff On Jul 29, 2010, at 11:39 PM, Andreas J. Koenig wrote: On Fri, 30 Jul 2010 00:19:41 -0500, Todd Rinaldo to...@cpanel.net said: Looking at some of the test reports from some of my personal modules, it looks like there are currently no automated test systems for perl 5.6. I would like to contribute some perl 5.6 automated smokers to the cause, but do not know where to start. There seems to be alot of projects running around which are working on the problem, but after looking around for the last hour, I'm even more confused about how to go about setting one up. Can anyone point me to a howto on this topic? http://wiki.cpantesters.org/ good enough? Unfortunately perl 5.6.2 doesn't build OK anymore on my linux smoke box. It spews out warnings about signals and this is why I have no 5.6.2 smoker. If somebody knows how to work around this, I'm willing to smoke 5.6.2 again. -- andreas
Re: Automated testing how to?
Getting it all working on older Perls isn't always that easy. For example Test::Reporter::Transport::Socket won't install on 5:005:3 because it needs warnings, which I can't get on that machine (install warnings tries to install Perl 5.12): Test-Reporter-Transport-Socket-0.12 Test-Reporter-Transport-Socket-0.12/dist.ini Test-Reporter-Transport-Socket-0.12/lib/Test/Reporter/Transport Test-Reporter-Transport-Socket-0.12/lib/Test/Reporter/Transport/Socket.pm Test-Reporter-Transport-Socket-0.12/t Test-Reporter-Transport-Socket-0.12/t/01_args.t Test-Reporter-Transport-Socket-0.12/META.yml Test-Reporter-Transport-Socket-0.12/LICENSE Test-Reporter-Transport-Socket-0.12/README Test-Reporter-Transport-Socket-0.12/MANIFEST Test-Reporter-Transport-Socket-0.12/META.json Test-Reporter-Transport-Socket-0.12/t/release-pod-syntax.t Test-Reporter-Transport-Socket-0.12/t/release-pod-coverage.t Test-Reporter-Transport-Socket-0.12/t/00-compile.t Test-Reporter-Transport-Socket-0.12/Changes Test-Reporter-Transport-Socket-0.12/Makefile.PL CPAN.pm: Going to build B/BI/BINGOS/Test-Reporter-Transport-Socket-0.12.tar.gz Can't locate warnings.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503) at Makefile.PL line 3. BEGIN failed--compilation aborted at Makefile.PL line 3. make: no target to make. /usr/bin/make -- NOT OK Running make test Oops, make had returned bad status Running make install Oops, make had returned bad status cpan install warnings Running make for J/JE/JESSE/perl-5.12.1.tar.gz -Nigel
Re: Automated testing how to?
Todd, I can active a 5.6.1 smoker. Would that help (I know that you asked for a 5.6.2)? -Nigel
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 11:21:26AM +0100, Nigel Horne wrote: Getting it all working on older Perls isn't always that easy. For example Test::Reporter::Transport::Socket won't install on 5:005:3 because it needs warnings, which I can't get on that machine (install warnings tries to install Perl 5.12): Test-Reporter-Transport-Socket-0.12 Test-Reporter-Transport-Socket-0.12/dist.ini Test-Reporter-Transport-Socket-0.12/lib/Test/Reporter/Transport Test-Reporter-Transport-Socket-0.12/lib/Test/Reporter/Transport/Socket.pm Test-Reporter-Transport-Socket-0.12/t Test-Reporter-Transport-Socket-0.12/t/01_args.t Test-Reporter-Transport-Socket-0.12/META.yml Test-Reporter-Transport-Socket-0.12/LICENSE Test-Reporter-Transport-Socket-0.12/README Test-Reporter-Transport-Socket-0.12/MANIFEST Test-Reporter-Transport-Socket-0.12/META.json Test-Reporter-Transport-Socket-0.12/t/release-pod-syntax.t Test-Reporter-Transport-Socket-0.12/t/release-pod-coverage.t Test-Reporter-Transport-Socket-0.12/t/00-compile.t Test-Reporter-Transport-Socket-0.12/Changes Test-Reporter-Transport-Socket-0.12/Makefile.PL CPAN.pm: Going to build B/BI/BINGOS/Test-Reporter-Transport-Socket-0.12.tar.gz Can't locate warnings.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503) at Makefile.PL line 3. BEGIN failed--compilation aborted at Makefile.PL line 3. make: no target to make. /usr/bin/make -- NOT OK Running make test Oops, make had returned bad status Running make install Oops, make had returned bad status cpan install warnings Running make for J/JE/JESSE/perl-5.12.1.tar.gz Try installing warnings::compat for 5.6 perls. -- Chris Williams aka BinGOs PGP ID 0x4658671F http://www.gumbynet.org.uk == pgpJ5tKdmkdkL.pgp Description: PGP signature
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 06:39, Andreas J. Koenig andreas.koenig.7os6v...@franz.ak.mind.de wrote: Unfortunately perl 5.6.2 doesn't build OK anymore on my linux smoke box. It spews out warnings about signals and this is why I have no 5.6.2 smoker. If somebody knows how to work around this, I'm willing to smoke 5.6.2 again. Have you tried building the maint-5.6 branch from Git instead of the 5.6.2 release?
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 8:59 AM, Ævar Arnfjörð Bjarmason ava...@gmail.com wrote: On Fri, Jul 30, 2010 at 06:39, Andreas J. Koenig andreas.koenig.7os6v...@franz.ak.mind.de wrote: Unfortunately perl 5.6.2 doesn't build OK anymore on my linux smoke box. It spews out warnings about signals and this is why I have no 5.6.2 smoker. If somebody knows how to work around this, I'm willing to smoke 5.6.2 again. Have you tried building the maint-5.6 branch from Git instead of the 5.6.2 release? In my github repo (git://github.com/dagolden/perl.git) I have a maint-5.6.2 branch as well as maint-5.x.y for everything from 5.6.1 to 5.8.8. Personally, I see no value in testing anything before 5.6.2 and only minimal value even testing that now that 5.12 is the current production release. -- David
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 13:16, David Golden xda...@gmail.com wrote: On Fri, Jul 30, 2010 at 8:59 AM, Ævar Arnfjörð Bjarmason ava...@gmail.com wrote: On Fri, Jul 30, 2010 at 06:39, Andreas J. Koenig andreas.koenig.7os6v...@franz.ak.mind.de wrote: Unfortunately perl 5.6.2 doesn't build OK anymore on my linux smoke box. It spews out warnings about signals and this is why I have no 5.6.2 smoker. If somebody knows how to work around this, I'm willing to smoke 5.6.2 again. Have you tried building the maint-5.6 branch from Git instead of the 5.6.2 release? In my github repo (git://github.com/dagolden/perl.git) I have a maint-5.6.2 branch as well as maint-5.x.y for everything from 5.6.1 to 5.8.8. Personally, I see no value in testing anything before 5.6.2 and only minimal value even testing that now that 5.12 is the current production release. There are still modules like YAML::Syck (that I and toddr now maintain) which maintain 5.6 compatibility. Having smokers on 5.6 is a valuable service for them. Having smokers on releases that aren't the latest on their branch is also valuable. Some people still run 5.6.*, 5.8.*, 5.10.* with * != 2, 9 1. E.g. Module::Install recently broke on =5.8.3. A lot of modules are doing use 5.006, or 5.008, while really only being compatible with 5.6.2 or 5.8.8. Holding them to it is a useful service.
Re: Automated testing how to?
On 30/07/10 13:45, Chris 'BinGOs' Williams wrote: Try installing warnings::compat for 5.6 perls. Thanks for the suggestion, but that failed: cpan install warnings::compat Going to read /root/.cpan/sources/authors/01mailrc.txt.gz Going to read /root/.cpan/sources/modules/02packages.details.txt.gz Scanning cache /root/.cpan/build for sizes There's a new CPAN.pm version (v1.9402) available! You might want to try install Bundle::CPAN reload cpan without quitting the current session. It should be a seamless upgrade while we are running... Going to read /root/.cpan/sources/modules/03modlist.data.gz Running make for S/SA/SAPER/warnings-compat-0.07.tar.gz CPAN: Net::FTP loaded ok Fetching with Net::FTP: ftp://ftp.mirror.8086.net/sites/CPAN/authors/id/S/SA/SAPER/warnings-compat-0.07.tar.gz CPAN: MD5 security checks disabled because MD5 not installed. Please consider installing the MD5 module. warnings-compat-0.07/ warnings-compat-0.07/Changes warnings-compat-0.07/eg/ warnings-compat-0.07/eg/warnings-register.pl warnings-compat-0.07/eg/warnings.pl warnings-compat-0.07/lib/ warnings-compat-0.07/lib/warnings/ warnings-compat-0.07/lib/warnings/compat.pm warnings-compat-0.07/lib/warnings/register.pm warnings-compat-0.07/lib/warnings.pm warnings-compat-0.07/Makefile.PL warnings-compat-0.07/MANIFEST warnings-compat-0.07/META.yml warnings-compat-0.07/README warnings-compat-0.07/t/ warnings-compat-0.07/t/00-load.t warnings-compat-0.07/t/distchk.t warnings-compat-0.07/t/pod.t warnings-compat-0.07/t/podcover.t warnings-compat-0.07/t/portfs.t warnings-compat-0.07/t/warnings.t CPAN.pm: Going to build S/SA/SAPER/warnings-compat-0.07.tar.gz Checking if your kit is complete... Looks good Warning: prerequisite Test::More 0 not found at (eval 1) line 219. 'LICENSE' is not a known MakeMaker parameter name. Writing Makefile for warnings Dependencies detected during [S/SA/SAPER/warnings-compat-0.07.tar.gz] - Test::More Running make test Make had some problems, maybe interrupted? Won't test Running make install Make had some problems, maybe interrupted? Won't install Running make for M/MS/MSCHWERN/Test-Simple-0.94.tar.gz CPAN: MD5 security checks disabled because MD5 not installed. Please consider installing the MD5 module. Test-Simple-0.94/ Test-Simple-0.94/.perlcriticrc Test-Simple-0.94/.perltidyrc Test-Simple-0.94/Changes Test-Simple-0.94/examples/ Test-Simple-0.94/examples/indent.pl Test-Simple-0.94/examples/subtest.t Test-Simple-0.94/lib/ Test-Simple-0.94/lib/Test/ Test-Simple-0.94/lib/Test/Builder/ Test-Simple-0.94/lib/Test/Builder/IO/ Test-Simple-0.94/lib/Test/Builder/IO/Scalar.pm Test-Simple-0.94/lib/Test/Builder/Module.pm Test-Simple-0.94/lib/Test/Builder/Tester/ Test-Simple-0.94/lib/Test/Builder/Tester/Color.pm Test-Simple-0.94/lib/Test/Builder/Tester.pm Test-Simple-0.94/lib/Test/Builder.pm Test-Simple-0.94/lib/Test/More.pm Test-Simple-0.94/lib/Test/Simple.pm Test-Simple-0.94/lib/Test/Tutorial.pod Test-Simple-0.94/Makefile.PL Test-Simple-0.94/MANIFEST Test-Simple-0.94/MANIFEST.SKIP Test-Simple-0.94/META.yml Test-Simple-0.94/README Test-Simple-0.94/SIGNATURE Test-Simple-0.94/t/ Test-Simple-0.94/t/00compile.t Test-Simple-0.94/t/00test_harness_check.t Test-Simple-0.94/t/bad_plan.t Test-Simple-0.94/t/bail_out.t Test-Simple-0.94/t/BEGIN_require_ok.t Test-Simple-0.94/t/BEGIN_use_ok.t Test-Simple-0.94/t/buffer.t Test-Simple-0.94/t/Builder/ Test-Simple-0.94/t/Builder/Builder.t Test-Simple-0.94/t/Builder/carp.t Test-Simple-0.94/t/Builder/create.t Test-Simple-0.94/t/Builder/current_test.t Test-Simple-0.94/t/Builder/current_test_without_plan.t Test-Simple-0.94/t/Builder/details.t Test-Simple-0.94/t/Builder/done_testing.t Test-Simple-0.94/t/Builder/done_testing_double.t Test-Simple-0.94/t/Builder/done_testing_plan_mismatch.t Test-Simple-0.94/t/Builder/done_testing_with_no_plan.t Test-Simple-0.94/t/Builder/done_testing_with_number.t Test-Simple-0.94/t/Builder/done_testing_with_plan.t Test-Simple-0.94/t/Builder/fork_with_new_stdout.t Test-Simple-0.94/t/Builder/has_plan.t Test-Simple-0.94/t/Builder/has_plan2.t Test-Simple-0.94/t/Builder/is_fh.t Test-Simple-0.94/t/Builder/is_passing.t Test-Simple-0.94/t/Builder/maybe_regex.t Test-Simple-0.94/t/Builder/no_diag.t Test-Simple-0.94/t/Builder/no_ending.t Test-Simple-0.94/t/Builder/no_header.t Test-Simple-0.94/t/Builder/no_plan_at_all.t Test-Simple-0.94/t/Builder/ok_obj.t Test-Simple-0.94/t/Builder/output.t Test-Simple-0.94/t/Builder/reset.t Test-Simple-0.94/t/Builder/reset_outputs.t Test-Simple-0.94/t/Builder/try.t Test-Simple-0.94/t/c_flag.t Test-Simple-0.94/t/circular_data.t Test-Simple-0.94/t/cmp_ok.t Test-Simple-0.94/t/dependents.t Test-Simple-0.94/t/diag.t Test-Simple-0.94/t/died.t Test-Simple-0.94/t/dont_overwrite_die_handler.t Test-Simple-0.94/t/eq_set.t Test-Simple-0.94/t/exit.t Test-Simple-0.94/t/explain.t Test-Simple-0.94/t/extra.t Test-Simple-0.94/t/extra_one.t Test-Simple-0.94/t/fail-like.t Test-Simple-0.94/t/fail-more.t
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 1:13 PM, Todd Rinaldo to...@cpanel.net wrote: Agreed. As evidenced by the page names. Which means we have no instructions for non-beta reporters. I'm also unclear if my beta reports will eventually propogate to the regular testers reports. Can you tell me? It's sort of a long term beta now. All the beta reports go into the main www.cpantesters.org database. They fail as root. I think it's the old OSX issue with root's home dir. I created an unprivileged cpants account on my box and now it's working better. Ok. I'll see if there's a way to detect that and fail gracefully. For what it's worth, you should never be smoke testing as root on any machine you care about. (Testing means running arbitrary code uploaded by someone you don't know -- not a good idea to do with root privileges) One thing I'm unclear on at this point. Is there any reason at this point a new user would use the 1.0 system directly? If so I can just phrase the instructions as If you're a new user, do this...; A new user should *NOT* use the 1.0 system as it will be retired at the end of August. New users should try 2.0 and report back here (as you've done) with any issues so we can address them. -- David
Re: Automated testing how to?
On Jul 30, 2010, at 12:25 PM, David Golden wrote: They fail as root. I think it's the old OSX issue with root's home dir. I created an unprivileged cpants account on my box and now it's working better. Ok. I'll see if there's a way to detect that and fail gracefully. For what it's worth, you should never be smoke testing as root on any machine you care about. (Testing means running arbitrary code uploaded by someone you don't know -- not a good idea to do with root privileges) I agree and thus the cpants account I setup. However my perl is installed as root and thus perl modules via cpanp have to be installed as root. I suppose I could use a different strategy to install perl. I definitely need more tuits. Thanks for your help David
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 12:56:52PM -0400, David Golden wrote: On Fri, Jul 30, 2010 at 12:21 PM, Todd Rinaldo to...@cpanel.net wrote: I hope that this email does not come off as insulting in any way. I didn't take it that way. It's really helpful to have feedback from someone new because we don't always understand what isn't obvious. Likewise, thanks for the feedback it is really useful. I had all the good intentions of starting a new VM on my work box and go through all the steps. However, the YAPC::Surveys, work and family have had to take precedence. 2a. Stumbling around I found this page http://devel.cpantesters.org/#smoker. 2b. Many links are broken there. Some declare themselves deprecated when you search harder. poe-component-cpan-reporter for instance. This is my fault. I updated the links a while ago and mistakenly typed a global replace with '.dist' instead of '/dist'. Fixed now. 3a. The page starts out talking about needing to choose between CPAN or CPANPLUS. It offers no optinion That is a philosophical debate beyond the scope of CPAN Testers. Generally the answer is whichever you would normally use. It generally comes down to, what do you use to install your module from the command line? CPAN or CPANPLUS? It's a personal choice, but you're right we should mention that :) I have to prepare for YAPC::Europe next week, so I'm not sure how much time I'm going to have to add the right things to the wiki. Likewise, I imagine that Chris Williams (responsible for CPANPLUS-YACSmoke) is also going to be busy next week too. BTW, CPANTS != CPAN Testers, two very different projects :) Thanks for all the feedback, it'll prove useful to help us embelish the guides in the right places. Cheers, Barbie. -- Birmingham Perl Mongers http://birmingham.pm.org Memoirs Of A Roadie http://barbie.missbarbell.co.uk CPAN Testers Blog http://blog.cpantesters.org YAPC Conference Surveys http://yapc-surveys.org Ark Appreciation Pages http://ark.eology.org
Re: Automated testing how to?
On Jul 30, 2010, at 11:08 AM, Barbie wrote: That is a philosophical debate beyond the scope of CPAN Testers. Generally the answer is whichever you would normally use. It generally comes down to, what do you use to install your module from the command line? CPAN or CPANPLUS? It's a personal choice, but you're right we should mention that :) Also cpanminus. Does it submit reports? Best, David
Re: Automated testing how to?
On Fri, Jul 30, 2010 at 2:46 PM, David E. Wheeler da...@kineticode.com wrote: On Jul 30, 2010, at 11:08 AM, Barbie wrote: That is a philosophical debate beyond the scope of CPAN Testers. Generally the answer is whichever you would normally use. It generally comes down to, what do you use to install your module from the command line? CPAN or CPANPLUS? It's a personal choice, but you're right we should mention that :) Also cpanminus. Does it submit reports? No. By deliberate decision on Miyagawa's part, since it's a tiny self-contained CPAN client. David
Re: Automated testing how to?
On Fri, 30 Jul 2010 12:59:10 +, Ævar Arnfjörð Bjarmason ava...@gmail.com said: On Fri, Jul 30, 2010 at 06:39, Andreas J. Koenig andreas.koenig.7os6v...@franz.ak.mind.de wrote: Unfortunately perl 5.6.2 doesn't build OK anymore on my linux smoke box. It spews out warnings about signals and this is why I have no 5.6.2 smoker. If somebody knows how to work around this, I'm willing to smoke 5.6.2 again. Have you tried building the maint-5.6 branch from Git instead of the 5.6.2 release? I hadn't but I just tried it and it also didn't get the signals right. But at least I could edit config.h manually to fill in the contents of 'kill -l'. That worked indeed and I now have a working 5.6.2 again. Thanks for the suggestion! After that I installed with force: CPAN::Reporter, HTML::Parser, URI (all of them didn't pass wome tests). Then Test::Reporter::Transport::Metabase and Crypt::SSLeay could be installed without force. But then CPAN::Reporter refused to run telling me that it was not installed (while it was). Key was finally to install File::HomeDir manually (with cp). And after that I sent my first Metabase report with a perl 5.6.2: [2010-07-31T03:38:45Z] [Andreas J. K�nig (ANDK)] [pass] [NWCLARK/Acme-Meta-0.02.tar.gz] [x86_64-linux] [perl-v5.6.2] I'm starting to smoke it now. -- andreas
