Skip Menu |

This queue is for tickets about the Schedule-Cron CPAN distribution.

Report information
The Basics
Id: 68615
Status: resolved
Priority: 0/
Queue: Schedule-Cron

People
Owner: Nobody in particular
Requestors: tlhackque [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in:
  • 1.01_1
  • 1.01_2
Fixed in: (no value)



Subject: Test issues
Tests could use some cleanup - lots of "uninitialized" errors in t/execution_time.t: $ampm when building under perl 5.12.3 X86_64-linux- thread-multi && Linux hagrid 2.6.35.13-91.fc14.x86_64 #1 SMP Tue May 3 13:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Not urgent in that it installs, but the screen full of errors is ugly. (I also had a lot of failures from mirror sites "not found", but eventually found one with the kit.) CPAN.pm: Going to build R/RO/ROLAND/Schedule-Cron-1.01_2.tar.gz Creating new 'MYMETA.yml' with configuration results Creating new 'Build' script for 'Schedule-Cron' version '1.01_2' Building Schedule-Cron ROLAND/Schedule-Cron-1.01_2.tar.gz ./Build -- OK Running Build test t/after_job.t ........... ok t/callbackreschedule.t .. ok t/delete_entry.t ........ ok t/dst_back.t ............ ok t/entry.t ............... ok t/execution_time.t ...... Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 47. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 120. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 121. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 124. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 125. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 126. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 127. t/execution_time.t ...... 1/52 Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. Use of uninitialized value $ampm in uc at /usr/share/perl5/Time/ParseDate.pm line 733, <DATA> line 142. t/execution_time.t ...... ok t/kwalitee.t ............ skipped: Test::Kwalitee not installed; skipping t/load_crontab.t ........ ok t/nofork.t .............. ok t/pod.t ................. ok t/pod_coverage.t ........ ok t/pretty_print_args.t ... ok t/sighandler.t .......... ok t/startup.t ............. ok All tests successful. Files=14, Tests=95, 26 wallclock secs ( 0.09 usr 0.05 sys + 0.99 cusr 0.20 csys = 1.33 CPU) Result: PASS ROLAND/Schedule-Cron-1.01_2.tar.gz ./Build test -- OK R
That's an issue of Time::ParseDate. What version are you using ? 

--> perl -MTime::ParseDate -e 'print $Time::ParseDate::VERSION,"\n"'

I had the same issue, after upgrading to 2011.0517, the warnings
disapeared (and they didn't occur in older version of Time::ParseDate either)

Maybe I should upgrade the version requirement of Time::ParseDate, too.

From: tlhackque [...] yahoo.com
If you have known issue, yes updating the dependency would be a good thing. perl -MTime::ParseDate -e 'print $Time::ParseDate::VERSION,"\n"' 2006.0814 I updated to 2011.0517, which resolved the problem. The odd thing is that I have a script that checks the installed versions of everything against CPAN released versions every week. Despite an 11-May releasse of 2011.0517, it doesn't show up as outdated... On Thu Jun 02 16:52:05 2011, ROLAND wrote: Show quoted text
> That's an issue of Time::ParseDate. What version are you using ? > > --> perl -MTime::ParseDate -e 'print $Time::ParseDate::VERSION,"\n"' > > I had the same issue, after upgrading to 2011.0517, the warnings > disapeared (and they didn't occur in older version of Time::ParseDate > either) > > Maybe I should upgrade the version requirement of Time::ParseDate, > too.
Added dependency on the lates Time::ParseDate in Build.PL and Make.PL so the warnings wont occur anymore.