Michael McCandless wrote:
I'll remove those 2 test cases.
The build now works perfectly. Thanks Mike!
--
Sami Siren
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
Hey Sami, I've been running tests quite a bit recently with Ubuntu 8.10
and OpenJDK 6 on a 64-bit machine, and I have not seen it once.
Just tried again with Sun JDK 6 and 5 32-bit as well, and I am still not
seeing it.
Odd.
- Mark
Sami Siren wrote:
I am constantly seeing following error
Ok, it's not a java 1.6 thing it's something else. I also found a box
that runs that test ok.
--
Sami Siren
Mark Miller wrote:
Hey Sami, I've been running tests quite a bit recently with Ubuntu
8.10 and OpenJDK 6 on a 64-bit machine, and I have not seen it once.
Just tried again with Sun JDK
Ok, it's not a java 1.6 thing it's something else. I also found a
box that runs that test ok.
From what I can tell, this is the test that's failing:
http://www.krugle.org/kse/entfiles/lucene/apache.org/java/trunk/src/test/org/apache/lucene/index/TestIndexInput.java#89
This is verifying that
I am constantly seeing following error when running ant test:
[junit] Testcase:
testRead(org.apache.lucene.index.TestIndexInput):FAILED
[junit] expected:[] but was:[??]
[junit] junit.framework.ComparisonFailure: expected:[] but was:[??]
[junit] at
I think your on the right tack Ken. Don't know enough about Unicode
myself, but I was looking at this this morning, and what you say
somewhat jives with what I saw.
I don't think you can just flip that switch though - the index format
will not match what its trying to read (having been
In fact I think the 2 test cases of the modified UTF8 null bytes are
just bogus, because they are using Java's UTF8 charset decoder to
construct a String when (as Ken points out) the byte sequence 0xC0
0x80 is illegal UTF8.
I'll remove those 2 test cases.
Mike
Mark Miller wrote:
I think your
