I checked out the commit hash and re-ran the test with the same seed,
it doesn't fail. I only ran the test twice, once with
TieredStopAtLevel=1 and once without that.

Given that the stacktrace looks "impossible", i suspect this might be
an openjdk issue? I assume this test usually reproduces failures for
given random seeds?

On Wed, Dec 8, 2021 at 12:44 PM Robert Muir <[email protected]> wrote:
>
> Uwe, it looks a little crazy:
>
> we've got asserts here that "index" is in bounds and certainly not -1
> right before the method call!
> https://github.com/apache/lucene/blob/main/lucene/core/src/java/org/apache/lucene/codecs/lucene90/Lucene90DocValuesProducer.java#L1123-L1125
>
> On Wed, Dec 8, 2021 at 12:33 PM Uwe Schindler <[email protected]> wrote:
> >
> > I updated the dependencies of Solr's main branch to Lucene 9.0
> >
> > On Mac and Linux, the following error occurs sometimes:
> > https://jenkins.thetaphi.de/job/Solr-main-Linux/2070/testReport/junit/org.ap
> > ache.solr.request/SimpleFacetsTest/testRangeFacetFilterVsDocValuesRandom/
> > https://jenkins.thetaphi.de/job/Solr-main-MacOSX/517/testReport/junit/org.ap
> > ache.solr/TestRandomDVFaceting/testRandomFaceting/
> >
> > "ArrayIndexOutOfBoundsException: Index -1 out of bounds for length 1" at
> > org.apache.lucene.util.packed.DirectMonotonicReader.get(DirectMonotonicReade
> > r.java:161)
> >
> > This looks like a bug (or is Solr not using something with docvalues
> > correctly, but an AIOOBE should not happen)!
> >
> > When searching through the failure mails, it looks like this was already
> > there with the Lucene preview from summer 2021.
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > https://www.thetaphi.de
> > eMail: [email protected]
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to