[LUCENENET-149] Current State of 2.3.1

• Type: Test
• Status: Closed
• Priority: Blocker
• Resolution: Won't Fix
• Assignee: Digy
• Reporter: Digy
• Created: 05/Sep/08 21:03
• Updated: 15/Nov/08 00:11
• Resolved: 15/Nov/08 00:11

Description

I created this issue to simplify the case of many issues releated with 2.3.1 and their patches.

My Current state is:

Patches Applied to current revision:
-------------------------------------
SupportClass.patch (LUCENENET-135)
DocumentsWriter.patch (LUCENENET-145)
SegmentTermPositionVector.patch (LUCENENET-146)
FieldsReader.patch & TestStressIndexing2.patch (LUCENENET-143)
+
TestStressIndexing2.cs line ~547
if (Lucene.Net.Index.TestStressIndexing2.sameFieldOrder) ---> if (Lucene.Net.Index.TestStressIndexing2.sameFieldOrder || true)

Failed Tests:
1-
TestIndexWriterLockRelease/LuceneTestCase.TestDummy

2-
TestSpans/TestSpansNearOrdered02
TestSpans/TestSpansNearOrdered03
TestSpans/TestSpansNearOrdered04
TestSpans/TestSpansNearOrdered05
These tests can pass if we change the static method of Similarity.cs as followsLUCENENET-144)
static Similarity()
{
for (int i = 0; i < 256; i++)

{ NORM_TABLE[i] = SmallFloat.Byte315ToFloat((byte)i); }

NORM_TABLE[119] = 0.447213595499958f; //which was 0.4375 originally.
}
(Since 0.447213595499958f is one of the possible values of NORM_TABLE[119], can these tests be thought as "PASSED"?)

3-
TestHugeRamFile/TestHugeFile

DIGY