Subject: | 30-patroarchy.t hangs on Windows |
I activated your debugging statements.
ok 1 - lock
ok 2 - unlock
ok 3 - unlock without possession fails
ok 4 - errno set
ok 5 - warning written
ok 6 - lock
ok 7 - non-blocking lock failed
ok 8 - non-blocking lock returned quickly
ok 9 - timed lock failed
ok 10 - ... errno set
ok 11 - ... without warning
ok 12 - timed lock took time
ok 13 - released resource
ok 14 - lock immediately accessible by new monitor
ok 15 - release reference from new monitor
ok 16 - got lock
ok 17 - stacked lock
ok 18 - stacked lock again
ok 19 - unlock with count
ok 20 - lock not available for new monitor
ok 21 - errno set
ok 22 - ... without additional warning
ok 23 - unlock with count too high ok
ok 24 - ... but generates warning
ok 25 - lock available after 2nd unlock
ok 26 - lock released from new monitor
# wait/notify fork -992 launch
# # STEP 1 - 1
ok 27 - wait fails without lock
ok 28 - errno set
ok 29 - notify fails without lock
ok 30 - errno set
ok 31 - eventually got lock
# # STEP 2 - 1
not ok 32 - ... but it took a while
# Failed test '... but it took a while'
# at 30-patroarchy.t line 95.
ok 33 - notify ok
# # STEP 3 - 0 but true
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 33.
(hangs here)
--
Alexandr Ciornii, http://chorny.net