Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
New
Description
eg https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/1566/consoleText
It seems it fails regularly. rcmuir came up with a clue
The test expects a ParseException (which contains offset) to be triggered for the invalid data.
But the offset isn't what the test expects.
If you look at the test and the code, there isn't anything sneaky going on here. We just populate the ParseException with getLineNumber.
Does this only fail with EA JDK? Could be a JDK issue!
NOTE: reproduce with: ant test -Dtestcase=TestDictionary -Dtests.method=testInvalidData -Dtests.seed=89954FC6F33225B1 -Dtests.multiplier=3 -Dtests.slow=true -Dtests.badapples=true -Dtests.locale=os-GE -Dtests.timezone=Pacific/Guadalcanal -Dtests.asserts=true -Dtests.file.encoding=US-ASCII
{{ [junit4] FAILURE 0.04s J2 | TestDictionary.testInvalidData <<<
[junit4] > Throwable #1: java.lang.AssertionError: expected:<24> but was:<23>
[junit4] > at __randomizedtesting.SeedInfo.seed([89954FC6F33225B1:61632831A7F4F9CE]:0)
[junit4] > at org.apache.lucene.analysis.hunspell.TestDictionary.testInvalidData(TestDictionary.java:137)}}