Sastry wrote: > Hi > I ran the individual test using /perl -Ilib ext/Time/HiRes/t/HiRes.t >> t.out 2>&1 and the contents of t.out are as follows > 1..31 > ok 1 > # have_gettimeofday = 1 > # have_usleep = 1 > # have_nanosleep = 0 > # have_ualarm = 1 > # have_clock_gettime = 0 > # have_clock_getres = 0 > # I am the main process 16843113, starting the timer process... > # The timer process 66151 launched, continuing testing... > ok 2 > ok 3 > # I am the timer process 66151, sleeping for 60 seconds... > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > [1] + Done(137) ./perl -Ilib ext/Time/HiRes/t/HiRes.t >t.out 2>&1 > 16843113 Killed ./perl > > Please let me know if there is anything specific to EBCDIC that makes
Hard to imagine that EBCDIC would cause the test to fail, I am more suspicious of z/OS. The test seems to hang while testing for ualarm(). The have_ualarm = 1 means that the probe found ualarm() in z/OS, but maybe there are some caveats in using that interface in z/OS? I am just guessing. > this test fail. > regards > Ravi Sastry
