From @masak

<TimToady> r​: gather loop { take my $foo; last; }
<camelia> rakudo-moar 5a38b2​: ( no output )
<camelia> ..rakudo-jvm 5a38b2​: OUTPUT«cannot connect to eval server​:
Connection refused␤»
<TimToady> masak​: ^^^ there's a minimal test case to blow up perl6-j
<TimToady> masak​: (that produces the error at
https://gist.github.com/anonymous/9dc73118674e46248155)

Exception in thread "main" org.perl6.nqp.runtime.UnwindException
at org.perl6.nqp.runtime.ThreadContext.<init>(ThreadContext.java​:120)
at org.perl6.nqp.runtime.GlobalContext.getCurrentThreadContext(GlobalContext.java​:335)
at org.perl6.nqp.runtime.GlobalContext.<init>(GlobalContext.java​:250)
at org.perl6.nqp.runtime.CompilationUnit.enterFromMain(CompilationUnit.java​:56)
at perl6.main(gen/jvm/main.nqp)

* masak submits rakudobug
<FROGGS> masak​: hold on
<FROGGS> might be the same as https://rt-archive.perl.org/perl6/Ticket/Display.html?id=122134
<TimToady> it might at that
<TimToady> otoh, if I remove the gather, it passes
<TimToady> so maybe not

From @usev6

I believe that some tests in S32-list/rotor.t (which use method 'rotor' with :partial) are dying for the same reason on rakudo.jvm

Method 'rotor' uses a construct like 'gather for @​bar { take $foo; last}' internally.

$ perl6-j -e '(1..3).rotor(2, :partial)'
Exception in thread "main" org.perl6.nqp.runtime.UnwindException
  at org.perl6.nqp.runtime.ThreadContext.<init>(ThreadContext.java​:120)
  at org.perl6.nqp.runtime.GlobalContext.getCurrentThreadContext(GlobalContext.java​:340)
  at org.perl6.nqp.runtime.GlobalContext.<init>(GlobalContext.java​:253)
  at org.perl6.nqp.runtime.CompilationUnit.enterFromMain(CompilationUnit.java​:56)
  at perl6.main(gen/jvm/main.nqp)

The evaluation runs fine when :partial is not needed​:

$ perl6-j -e 'say (1..2).rotor(2, :partial)'
1 2

$ perl6-j -e 'say (1..4).rotor(2, :partial)'
1 2 3 4

From @usev6

To me this looks like the same problem as https://rt-archive.perl.org/perl6/Ticket/Display.html?id=124279

I'm closing this old issue in favour of a new issue in the rakudo repo: rakudo/rakudo#3634