On 3 June 2011 01:47, Sean P. DeNigris <sean@clipperadams.com> wrote:
More info on hanging tests...
 UnixProcessAccessorTestCase    testIsExecutableForUserInGroup    testIsReadableForUserInGroup    testIsReadable    testIsWritable    testIsWritableForUserInGroup
All hang on line: OSProcess waitForCommand: 'touch /tmp/delete.me'.
UnixProcess>>waitForCommand: Â Â Â Â <snip> Â Â Â Â [proc runState == #complete] whileFalse: [d wait]. <-- infinite loop
This may be related to another problem I was having with CommandShell: Â p := PipeableOSProcess command: '/bin/echo this is a test'. Â result := p output. "hangs"
ExternalUnixOSProcess>>isComplete  ^ self runState == #complete from PipeableOSProcess(PipeJunction)>>isComplete from PipeableOSProcess(PipeJunction)>>outputOn: from PipeableOSProcess(PipeJunction)>>output
sounds like VM cannot detect that child process are finished (complete).
-- View this message in context: http://forum.world.st/OSProcess-on-1-2-tp3569458p3569593.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko AKA sig.