From @AlexDaniel

Code​:

sub get-output() {
  my $proc = Proc​::Async.new​: â��echoâ��, â��testâ��;
  react {
  #whenever $proc.stdout { } # â��â�� these work
  #whenever $proc.stderr { } #
  whenever $proc { } # â�� this doesn't
  whenever $proc.start { }
  }
  say $++;
}

loop { get-output }

The result depends on your luck. Sometimes it gets stuck on the second execution, sometimes it manages to do it over 20 times and then gets stuck.

According to this it is supposed to work​: https://irclog.perlgeek.de/perl6-dev/2017-07-12#i_14862898

I don't know if there's any trap I'm getting into, or if it's just a bug. Anyway, I hope a ticket won't hurt.

From @AlexDaniel

Alright! This was fixed.

Bisectable points at the merge of “better-sched” branch, which happen right after 2017.09 release. See rakudo/rakudo@61a77e6

Zoffix++ found some tests​: Raku/roast@ae3eea8

However, these tests are not enough to resolve this ticket. We'd need a stress test that does it in a loop several times, just like it is described in the OP.

In any case, this is no longer ANNOYING and is simply TESTNEEDED.

On 2017-07-17 21​:34​:25, alex.jakimenko@​gmail.com wrote​:

Code​:

sub get-output() {
my $proc = Proc​::Async.new​: ‘echo’, ‘test’;
react {
#whenever $proc.stdout { } # ←â�� these work
#whenever $proc.stderr { } #
whenever $proc { } # ← this doesn't
whenever $proc.start { }
}
say $++;
}

loop { get-output }

The result depends on your luck. Sometimes it gets stuck on the second
execution, sometimes it manages to do it over 20 times and then gets
stuck.

According to this it is supposed to work​:
https://irclog.perlgeek.de/perl6-dev/2017-07-12#i_14862898

I don't know if there's any trap I'm getting into, or if it's just a
bug. Anyway, I hope a ticket won't hurt.

From @zoffixznet

Stresstests in Raku/roast@e821843

@zoffixznet - Status changed from 'new' to 'resolved'