[
https://issues.apache.org/jira/browse/LUCENE-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4735:
---------------------------------------
Attachment: TestTreeMap2.java
Simple standalone test... if you run with J9 1.6, or at least with this version:
{noformat}
Java(TM) SE Runtime Environment (build pxa6460sr9fp2ifix-20111111_05(SR9
FP2+IV03622+IV02378+IZ99243+IZ97310+IV00707))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64
jvmxa6460sr9-20111111_94827 (JIT enabled, AOT enabled)
J9VM - 20111111_094827
JIT - r9_20101028_17488ifx45
GC - 20101027_AA)
JCL - 20110727_04
{noformat}
Then the test will print:
{noformat}
FAILED: subMap.lastKey=4545 but should be 4576
{noformat}
But with Oracle Java 1.6 it prints "OK".
> IBM J9 JVM causes test failure in Kuromoji's TestExtended
> ---------------------------------------------------------
>
> Key: LUCENE-4735
> URL: https://issues.apache.org/jira/browse/LUCENE-4735
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Attachments: LUCENE-4735.patch, TestTreeMap2.java
>
>
> Note that this is not a Lucene bug; it's a JVM bug, but I wanted to track it
> in Lucene as well in case others hit it.
> I noticed this test frequently fails when running under IBM's J9 JVM (1.6.0)
> ... and I finally tracked down the root cause and made a small test case, eg
> on trunk, rev 1439839, if you run:
> {noformat}
> ant test -Dtestcase=TestExtendedMode -Dtestmethod=testRandomHugeStrings
> -Dtests.seed=26D2B352E9603950
> {noformat}
> it fails with this:
> {noformat}
> [junit4:junit4] > Throwable #1: java.lang.IllegalArgumentException:
> startOffset must be non-negative, and endOffset must be >= startOffset,
> startOffset=4272,endOffset=4271
> [junit4:junit4] > at
> __randomizedtesting.SeedInfo.seed([26D2B352E9603950:BEF1D491B7168518]:0)
> [junit4:junit4] > at
> org.apache.lucene.analysis.tokenattributes.OffsetAttributeImpl.setOffset(OffsetAttributeImpl.java:45)
> [junit4:junit4] > at
> org.apache.lucene.analysis.ja.JapaneseTokenizer.incrementToken(JapaneseTokenizer.java:463)
> [junit4:junit4] > at
> org.apache.lucene.analysis.BaseTokenStreamTestCase.checkAnalysisConsistency(BaseTokenStreamTestCase.java:635)
> [junit4:junit4] > at
> org.apache.lucene.analysis.BaseTokenStreamTestCase.checkRandomData(BaseTokenStreamTestCase.java:546)
> [junit4:junit4] > at
> org.apache.lucene.analysis.BaseTokenStreamTestCase.checkRandomData(BaseTokenStreamTestCase.java:447)
> [junit4:junit4] > at
> org.apache.lucene.analysis.BaseTokenStreamTestCase.checkRandomData(BaseTokenStreamTestCase.java:375)
> [junit4:junit4] > at
> org.apache.lucene.analysis.ja.TestExtendedMode.testRandomHugeStrings(TestExtendedMode.java:76)
> {noformat}
> I've seen other analyzer tests fail with similar exceptions.
> I dug in, and found that there's a bug in TreeMap.subMap, and it's easily
> reproduced with a small test case, which I'll attach. I'll also open an
> issue with J9.
> I also found a workaround that seems to sidestep the bug for Lucene.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
