Up until a couple of weeks ago, all the threads tests
were passing on Cygwin. I had submitted a patch some
time ago that never got applied enabling tests for
threads, timer, and extend_13 that never got applied.
I figured there was good reason so I didn't say
anything about the tests failing except an occasional
"that's weird" on #parrot.
So today I decide to look at threads_2.pasm
It says at the bottom that the output could appear in
reversed order and so I am guessing the sleep
statement is to ensure that it comes out in the proper
order.
So - why is the test failing? Because the second
print statement never makes it to the screen.
If I remove the print statement entirely, I see both
things in the reverse expected order.
If I place the sleep statement after the main thread
print then all I get to the screen is the that and not
the print statement from thread 1
It is almost as if by the time the time the second
print happens, the filehandle is already closed
So - since threads aren't officially supposed to be
working on Cygwin - is this something I should care
about or not?
Cheers
Joshua Gatcomb
a.k.a. Limbic~Region
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
