On Jan 16, 4:50am, Steffen Beyer wrote:
>
> Hello Ed Allen Smith, in a previous mail you wrote:
>
> > This distribution has been tested as part of the cpan-testers
> > effort to test as many new uploads to CPAN as possible. See
> > http://testers.cpan.org/
> >
> > Please cc any replies to [EMAIL PROTECTED] to keep other
> > test volunteers informed and to prevent any duplicate effort.
> >
> > --
> > PERL_DL_NONLAZY=1 /usr/sbin/perl -Iblib/arch -Iblib/lib
>-I/usr/share/lib/perl5/5.6.0/IP30-R12000-irix -I/usr/share/lib/perl5/5.6.0 -e 'use
>Test::Harness qw(&runtests $verbose); $verbose=1; runtests @ARGV;' t/*.t
> > [...]
> > t/m006....1..33
> > ok 1
> > ok 2
> > ok 3
> > ok 4
> > ok 5
> > ok 6
> > ok 7
> > ok 8
> > ok 9
> > not ok 10
> > not ok 11
> > ok 12
> > ok 13
> > ok 14
> > ok 15
> > ok 16
> > ok 17
> > ok 18
> > ok 19
> > ok 20
> > ok 21
> > ok 22
> > ok 23
> > ok 24
> > ok 25
> > ok 26
> > ok 27
> > ok 28
> > ok 29
> > ok 30
> > ok 31
> > ok 32
> > ok 33
> > FAILED tests 10-11
> > Failed 2/33 tests, 93.94% okay
> > [...]
> > Failed 1/47 test scripts, 97.87% okay. 2/2923 subtests failed, 99.93% okay.
> > Failed Test Stat Wstat Total Fail Failed List of Failed
> > -------------------------------------------------------------------------------
> > t/m006.t 33 2 6.06% 10-11
> > gmake: *** [test_dynamic] Error 9
> > [...]
>
> Could you please "make install" the module anyway
I actually simply ran it as make test TEST_VERBOSE=1,
uninstalled. TEST_VERBOSE=1 lets the makefile know to set $verbose=1
for Test::Harness, which in turn lets it produce the script's output
(instead of just the "ok #") on STDOUT. (Printing the results to
STDERR, which goes directly to the user, would be another
possibility.)
> and run a modified "m006.t" test script with "perl m006.t" and send
> me the output? (To modify m006.t, see the attached patch)
>
> I suspect that your system (Irix) has a broken "mktime"
> implementation.
I suspect as much also:
t/m006....1..33
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
not ok 10
Date::Calc::mktime(): date out of range at t/m006.t line 66
not ok 11
172800
BTW, I also modified it to print out the
result of $date->date_format(3) for the output of localtime(0); it was
"Wednesday, December 31st 1969 19:00:00". Looks OK, at least if mktime
is properly using the local timezone (EST5EDT).
> Another person has already reported a similar problem (it turned out
> that his "localtime" was not accepting INTMAX = 0x7FFFFFFF as an argument)
> which went away after installing an update for his OS:
>
> : We have installed patch 103640-37 from SunSolve onto that machine
> : (after finding that other Solaris 2.5.1 hosts would NOT exhibit the
> : problem). This fixes localtime() among a zillion things.
> : Now the installation of Date::Calc 5.0 works like a charm.
Interesting. I did a bug/patch search with SGI and didn't spot
anything.
> Hopefully the output of the modified m006.t test script will give
> us a hint of what's going wrong on your machine.
Indeed. I tried modifying it to use localtime(1), to see if it had a
problem returning a time of 0, and it also failed:
t/m006....1..33
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
# Wednesday, December 31st 1969 19:00:01
ok 9
not ok 10
Date::Calc::mktime(): date out of range at t/m006.t line 70
not ok 11
172800
Looks to me as if it isn't checking the TZ before it sees if the date
is valid/invalid... let's see... putting in a printing of
join(";",Timezone(0)) gives:
-1;11;30;19;0;0;0
If I try setting the TZ environment variable to GMT0, everything
works.
> Best regards,
And to you,
-Allen
P.S. BTW, what in the _world_ is:
$time = 172800;
if ($time == 172800)
{print "ok $n\n";} else {print "not ok $n\n";}
$n++;
doing as a part of m006.t? Am I misinterpreting something? I can see
the first line, but not the test...
--
Allen Smith [EMAIL PROTECTED]
September 11, 2001 A Day That Shall Live In Infamy II
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin
