On Fri, 22 Apr 2016 12:20:54 -0700, barto...@gmx.de wrote:
> On Thu Apr 21 04:41:32 2016, barto...@gmx.de wrote:
> > [...]
> > A somewhat golfed example of the hanging code is:
> >
> > $ perl6-j -e 'my $r = Supplier.new; my $s = $r.Supply; my $c =
> > $s.Channel; my $p = start { for @$c { } }; for 1..4 { $r.emit($_); };
> > $r.quit(X::AdHoc.new(:payload("foo"))); try await $p;'
>
> Today I've seen a hang with S17-supply/Channel.t on rakudo-m during
> a spectest. So I took a closer look. For some reasons I get
> substantially more hangs on my FreeBSD virtual machine than on a
> bare metal Debian box -- and not only for rakudo-j.
>
> The following numbers are for 100 runs of the mentioned commands:
>
> FreeBSD 10.3, OpenJDK 1.8 (virtual machine)
> ===========================================
> rakudo-m 463e7589a1
> * 0 hangs when running golfed code from command line (s.a.)
> * 61 hangs when running 'perl6-m -Ilib t/spec/S17-supply/Channel.t
> * 43 hangs when running 'perl t/harness --fudge --moar t/spec/S17-
> supply/Channel.t'
>
> rakudo-j 463e7589a1
> * 18 hangs when running golfed code from command line (s.a.)
> * many hangs when running 'perl6-j -Ilib t/spec/S17-supply/Channel.t
> * many hangs when running 'perl t/harness --fudge --jvm t/spec/S17-
> supply/Channel.t'
>
> Debian 7.9, OpenJDK 1.7
> =======================
> rakudo-m 463e7589a1
> * 0 hangs when running golfed code from command line (s.a.)
> * 0 hangs when running 'perl6-m -Ilib t/spec/S17-supply/Channel.t
> * 0 hangs when running 'perl t/harness --fudge --moar t/spec/S17-
> supply/Channel.t'
>
> rakudo-j 463e7589a1
> * 0 hangs when running golfed code from command line (s.a.)
> * 1 hang when running 'perl6-j -Ilib t/spec/S17-supply/Channel.t
> * 2 hangs when running 'perl t/harness --fudge --jvm t/spec/S17-
> supply/Channel.t'
I haven't seen a single hang in S17-supply/Channel.t on moar for many months.
Also, I just repeated my earlier experiment (running the golfed code and the
test file t/spec/S17-supply/Channel.t in a loop) and there was no problem at
all (neither on moar nor on jvm). Therefore I'm closing this ticket as
'resolved'.
