lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7032) jdk-9-ea+105 breaks MinimizeOperations.minimize()
Date Wed, 17 Feb 2016 17:27:18 GMT


Uwe Schindler commented on LUCENE-7032:

I think we are now fine to open bug report. I did this several times. Maybe use older bug
as template:
- How to checkout lucene-core (modify to use GIT)
- How to run the test (above command line)
- How to get pure "java" command line with "ant -verbose"

The OpenJDK developers (e.g., Roland Westrelin) were able to reproduce and debug. I think
thats enough. I would not spend too much time in debugging this.

> jdk-9-ea+105 breaks MinimizeOperations.minimize()
> -------------------------------------------------
>                 Key: LUCENE-7032
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: master
>            Reporter: Robert Muir
>              Labels: Java9
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message