Bug #98347 for Time-StasisField: native.t hangs on Windows

Wed Aug 27 02:12:30 2014 CHORNY [...] cpan.org - Ticket created

Subject:

native.t hangs on Windows

1..21 ok 1 - time returns the same value as CORE::time ok 2 - gmtime returns the same value as CORE::gmtime with no argument ok 3 - gmtime returns the same value as CORE::gmtime in scalar context ok 4 - gmtime returns the same value as CORE::gmtime in list context ok 5 - localtime returns the same value as CORE::localtime with no argument ok 6 - localtime returns the same value as CORE::localtime in scalar context ok 7 - localtime returns the same value as CORE::localtime in list context ok 8 - sleep returns the same value as CORE::sleep ok 9 - sleep does not pause runtime given a zero duration ok 10 - sleep does not pause runtime given a subsecond duration ok 11 - sleep pauses runtime for the correct amount given a nontrivial sleep time ok 12 - alarm initially returns 0 seconds not ok 13 - alarm returns the time remaining on the previous alarm # Failed test 'alarm returns the time remaining on the previous alarm' # at t/native.t line 54. # got: '0' # expected: '6000' not ok 14 - alarm does not support subsecond times # Failed test 'alarm does not support subsecond times' # at t/native.t line 55. # got: '0' # expected: '6000' not ok 15 - alarm treats prior negative alarms as undef # Failed test 'alarm treats prior negative alarms as undef' # at t/native.t line 56. # got: '0' # expected: undef not ok 16 - alarm triggers after appropriate number of seconds # Failed test 'alarm triggers after appropriate number of seconds' # at t/native.t line 64. # '3' # <= # '1' ok 17 - alarm triggers sigalarm ok 18 - alarm returns zero if the previous alarm triggered ok 19 - alarm is disabled when set to zero sleep(2147450879) too large at C:/strawberry182/cpan/build/Time-StasisField-0.01-yTBFue/t/../lib/Time/StasisField.pm line 320. (hangs) -- Alexandr Ciornii, http://chorny.net

Mon Sep 08 19:27:54 2014 MORNINDED [...] cpan.org - Correspondence added

Most of the failing tests seem to be around differences in how each system has chosen to implement the alarm function. The test in question is supposed to show that sleep without an argument is forever instead of never, which it seems to. However, the alarm isn't forcing the test to end like expected. Perhaps upping the timing to 2 seconds would work (consistent with some of the other timing discrepancies)? Otherwise I'm unsure. I don't have a windows machine so testing this code myself is a bit tough. Patches are welcome (preferred through github). On Wed Aug 27 02:12:30 2014, CHORNY wrote: Show quoted text

> 1..21 > ok 1 - time returns the same value as CORE::time > ok 2 - gmtime returns the same value as CORE::gmtime with no argument > ok 3 - gmtime returns the same value as CORE::gmtime in scalar context > ok 4 - gmtime returns the same value as CORE::gmtime in list context > ok 5 - localtime returns the same value as CORE::localtime with no > argument > ok 6 - localtime returns the same value as CORE::localtime in scalar > context > ok 7 - localtime returns the same value as CORE::localtime in list > context > ok 8 - sleep returns the same value as CORE::sleep > ok 9 - sleep does not pause runtime given a zero duration > ok 10 - sleep does not pause runtime given a subsecond duration > ok 11 - sleep pauses runtime for the correct amount given a nontrivial > sleep time > ok 12 - alarm initially returns 0 seconds > not ok 13 - alarm returns the time remaining on the previous alarm > # Failed test 'alarm returns the time remaining on the previous > alarm' > # at t/native.t line 54. > # got: '0' > # expected: '6000' > not ok 14 - alarm does not support subsecond times > # Failed test 'alarm does not support subsecond times' > # at t/native.t line 55. > # got: '0' > # expected: '6000' > not ok 15 - alarm treats prior negative alarms as undef > # Failed test 'alarm treats prior negative alarms as undef' > # at t/native.t line 56. > # got: '0' > # expected: undef > not ok 16 - alarm triggers after appropriate number of seconds > # Failed test 'alarm triggers after appropriate number of seconds' > # at t/native.t line 64. > # '3' > # <= > # '1' > ok 17 - alarm triggers sigalarm > ok 18 - alarm returns zero if the previous alarm triggered > ok 19 - alarm is disabled when set to zero > sleep(2147450879) too large at C:/strawberry182/cpan/build/Time- > StasisField-0.01-yTBFue/t/../lib/Time/StasisField.pm line 320. > (hangs)

Mon Sep 08 19:27:55 2014 The RT System itself - Status changed from 'new' to 'open'