On Thu, Nov 10, 2016 at 10:00 PM, <pet...@riseup.net> wrote: > Any > more ideas why? Is run-process blocking everyone? Is there some FFI call > like you mentioned? Where could I start to debug this on my own?
The only difference to what you are doing and what my test did was you're running as a script. So I tried this: -------------8<------------- USING: fry prettyprint kernel io namespaces sequences io.launcher io.directories io.encodings.utf8 io.files io.files.info io.pathnames concurrency.messaging threads math tools.threads accessors calendar ; IN: script self '[ "bash -c \"sleep 10\"" run-process drop 1 _ send ] "1" spawn self '[ "bash -c \"sleep 5\"" run-process drop 2 _ send ] "2" spawn receive . receive . clear -------------8<------------- With that I see what you are seeing. Both numbers print out after the last thread finishes. It looks like it's buffering in this case. If I add a 'flush' then I see them printed after 5 seconds then 10 seconds: -------------8<------------- USING: fry prettyprint kernel io namespaces sequences io.launcher io.directories io.encodings.utf8 io.files io.files.info io.pathnames concurrency.messaging threads math tools.threads accessors calendar ; IN: script self '[ "bash -c \"sleep 10\"" run-process drop 1 _ send ] "1" spawn self '[ "bash -c \"sleep 5\"" run-process drop 2 _ send ] "2" spawn receive . flush receive . flush clear -------------8<------------- Could this fix your issue? -- http://bluishcoder.co.nz ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
