[ 
https://issues.apache.org/jira/browse/LUCENE-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149918#comment-15149918
 ] 

Robert Muir commented on LUCENE-7032:
-------------------------------------

The flags passed by our jenkins randomization (-Dargs="-XX:+UseCompressedOops 
-XX:+UseParallelGC -XX:-UseSuperWord") are all irrelevant. It fails in the same 
way with any garbage collector and on/off for the other two.

So my reproduction line is something like this:

{noformat}
ant beast -Dtestcase=TestMinimize -Dtests.method="testBasic*" 
-Dtests.iters=1000 -Dtests.multiplier=3 -Dtests.seed=5E1BF6106DCA9EC9 
-Dtests.failfast=yes -Dbeast.iters=5 -Dtests.dups=8 -Dtests.jvms=8
{noformat}

I lowered beast.iters to 5, even though so far it always fails in the first 
iteration... we want to be careful since its only failing once per thousands 
(inefficient). This is probably good enough to slowly bisect hotspot to find 
the problematic commit, or we could play a guessing game with jvm flags. 
[~dawid.weiss], I know you have done this before: do you still have the 
bisection script? Maybe we should commit it to our dev-tools if you still have 
it around.

> jdk-9-ea+105 breaks MinimizeOperations.minimize()
> -------------------------------------------------
>
>                 Key: LUCENE-7032
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7032
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>
> As soon as jdk-9-ea+105 was put into test rotation, automaton tests have been 
> sporatically failing in non-reproducible ways. All of them invoke hopcroft 
> minimization either directly or indirectly.
> The bug manifests in several forms:
> * ArrayIndexOutOfBoundsException in minimize()
> * IllegalArgumentException for an explicit bounds check
> * incorrect resulting automaton
> This method is ... let's say not the ideal one to debug something like this, 
> but I've at least got it where I can make it fail in a few minutes with 
> beasting, so we can try simple things like turning on/off jvm flags to try to 
> narrow it more.
> It would be really great to make it fail more efficiently, but unfortunately 
> it takes many thousands of iterations until we understand more about it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to