-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proc::Async.kill doesn't seem to work when more than 1 proc is involved #6304
Comments
From @zoffixznetThis appears to hang more often than not, despite printing "Killing" messages. perl6 -e 'await ^2 .map: {start { with Proc::Async.new: $*EXECUTABLE, "-e", "sleep" -> $p { Promise.in(2).then: {say "Killing"; $p.kill: SIGTERM}; await $p.start } }}' However, if we reduce it to just 1 Proc, then it appears to work without issues, killing the spawned Proc every time: perl6 -e 'await ^1 .map: {start { with Proc::Async.new: $*EXECUTABLE, "-e", "sleep" -> $p { Promise.in(2).then: {say "Killing"; $p.kill: SIGTERM}; await $p.start } }}' This looks to be the code handling the kill op, but I don't know if it looks wrong or not: void MVM_proc_kill_async(MVMThreadContext *tc, MVMObject *handle_obj, MVMint64 signal) { |
From @zoffixznetFWIW, resolving this ticket will automatically resolve this roast Issue: Raku/roast#158 |
From @zoffixznetOn Thu, 01 Jun 2017 18:42:03 -0700, cpan@zoffix.com wrote:
Thank you for the report. This is now fixed. Fix: rakudo/rakudo@99421d4caa |
@zoffixznet - Status changed from 'new' to 'resolved' |
Migrated from rt.perl.org#131479 (status was 'resolved')
Searchable as RT131479$
The text was updated successfully, but these errors were encountered: