[concurrency-interest] Difficulty interpreting jcstress results

Andrew Haley aph at redhat.com
Thu Aug 22 09:41:47 EDT 2013

On 08/22/2013 01:02 PM, Aleksey Shipilev wrote:

> This seems to indicate the fatal error, not the test failure. Maybe
> the VM crashed after a while? The forked VM can still have
> communicated a few results before the crash.

I wouldn't be surprised.  It's still rather flakey.

> Let me see if I can get more reliable reporting in these cases.
> In the mean time, can you try to disable forking with "-f 0" and
> re-run the test selectively with "-t .*FloatBuffer.*"?

Everything runs just fine.


More information about the Concurrency-interest mailing list