I can't explain it, both JVMs emitted QUIT events so they should have terminated properly. There's nothing in the sysout spills. Next time you see this, should it happen again, don't terminate the build, Uwe, ok? I'd like to take some diagnostics (stack traces) from live JVMs.
Dawid On Sun, Sep 9, 2012 at 2:15 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote: > I'm taking it right now, nevermind. > > On Sun, Sep 9, 2012 at 2:12 PM, Dawid Weiss > <dawid.we...@cs.put.poznan.pl> wrote: >> Did you take the snapshot of the workbench (event) files, Uwe? >> >>> Interestingly the output is strange, the test runner did not even know >>> *where* the test hung. >> >> It's possible if the forked jvm hung in between suites. Not likely, >> but possible. >> >> Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
