Hi All:
Are all of the current patches for version 2.3.1 committed to/in SVN?
I tried building the latest sources and then running the unit tests; but I have
encounter a number of issues.
(1) Test-VS2005.sln Does not build "out of the box", these errors occur:
Error 1 Source file '.\src\Test\Index\Store\TestFSDirectory.cs' could not be
opened ('The system cannot find the file specified. ') Test-VS2005
Error 2 Source file '.\src\Test\Index\Store\FSDirectoryTestCase.cs' could not
be opened ('The system cannot find the file specified. ') Test-VS2005
Removing these two files from the VS Solution allows the compile to succeed.
(2) Unit Test, TestIndexWithThreads causes this exception:
An unhandled exception was detected. Since it was most likely thrown on a
separate thread, it may or may not have been caused by the current test.
System.SystemException: Internal error: 1 deleted 0 documents, term=id:92 at
Lucene.Net.Index.IndexThread.Run() in
.\src\Test\Index\TestIndexModifier.cs:line 328 at
System.Threading.ThreadHelper.ThreadStart_Context(Object state) at
System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state) at
System.Threading.ThreadHelper.ThreadStart()
(3) Unit Test, TestThreadSafety causes this exception:
An unhandled exception was detected. Since it was most likely thrown on a
separate thread, it may or may not have been caused by the current test.
NUnit.Framework.AssertionException: System.IndexOutOfRangeException: Index was
outside the bounds of the array. at
Lucene.Net.Index.DocumentsWriter.Abort(AbortException ae) in
.\src\Lucene.Net\Index\DocumentsWriter.cs:line 526 at
Lucene.Net.Index.DocumentsWriter.UpdateDocument(Document doc, Analyzer
analyzer, Term delTerm) in .\src\Lucene.Net\Index\DocumentsWriter.cs:line 2884
at Lucene.Net.Index.DocumentsWriter.AddDocument(Document doc, Analyzer
analyzer) in .\src\Lucene.Net\Index\DocumentsWriter.cs:line 2837 at
Lucene.Net.Index.IndexWriter.AddDocument(Document doc, Analyzer analyzer) in
.\src\Lucene.Net\Index\IndexWriter.cs:line 1562 at
Lucene.Net.Index.IndexWriter.AddDocument(Document doc) in
.\src\Lucene.Net\Index\IndexWriter.cs:line 1540 at
Lucene.Net.Index.TestPayloads.AnonymousClassThread.Run() in
.\src\Test\Index\TestPayloads.cs:line 77 at
NUnit.Framework.Assert.Fail(String message, Object[] args) at
NUnit.Framework.Assert.Fail(String message) at
Lucene.Net.Index.TestPayloads.AnonymousClassThread.Run() in
.\src\Test\Index\TestPayloads.cs:line 83 at
System.Threading.ThreadHelper.ThreadStart_Context(Object state) at
System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state) at
System.Threading.ThreadHelper.ThreadStart()
------------------------------------------------
The above two exceptions cause NUnit-gui.exe to crash.
I rebuild the Lucene.Net.Test DLL with these tests tagged as "Ignore". This
allows unit testing to proceed, but the following errors occur:
------------------------------------------------
(4) Unit Test, TestSpanNearOrdered02 fails:
expected <0>, but was <1>
at Lucene.Net.Search.CheckHits.CheckHits_Renamed(Query query, String
defaultFieldName, Searcher searcher, Int32[] results) in
.\src\Test\Search\CheckHits.cs:line 165
at Lucene.Net.Search.Spans.TestSpans.CheckHits(Query query, Int32[] results)
in .\src\Test\Search\Spans\TestSpans.cs:line 68
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3SQ(SpanQuery q1,
SpanQuery q2, SpanQuery q3, Int32 slop, Int32[] expectedDocs) in
.\src\Test\Search\Spans\TestSpans.cs:line 75
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3(Int32 slop, Int32[]
expectedDocs) in .\src\Test\Search\Spans\TestSpans.cs:line 80
at Lucene.Net.Search.Spans.TestSpans.TestSpanNearOrdered02() in
.\src\Test\Search\Spans\TestSpans.cs:line 102
(5) Unit Test, TestSpanNearOrdered03, fails:
expected <0>, but was <1>
at Lucene.Net.Search.CheckHits.CheckHits_Renamed(Query query, String
defaultFieldName, Searcher searcher, Int32[] results) in
.\src\Test\Search\CheckHits.cs:line 165
at Lucene.Net.Search.Spans.TestSpans.CheckHits(Query query, Int32[] results)
in .\src\Test\Search\Spans\TestSpans.cs:line 68
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3SQ(SpanQuery q1,
SpanQuery q2, SpanQuery q3, Int32 slop, Int32[] expectedDocs) in
.\src\Test\Search\Spans\TestSpans.cs:line 75
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3(Int32 slop, Int32[]
expectedDocs) in .\src\Test\Search\Spans\TestSpans.cs:line 80
at Lucene.Net.Search.Spans.TestSpans.TestSpanNearOrdered03() in
.\src\Test\Search\Spans\TestSpans.cs:line 108
(6) Unit Test, TestSpanNearOrdered04, fails:
expected <0>, but was <1>
at Lucene.Net.Search.CheckHits.CheckHits_Renamed(Query query, String
defaultFieldName, Searcher searcher, Int32[] results) in
.\src\Test\Search\CheckHits.cs:line 165
at Lucene.Net.Search.Spans.TestSpans.CheckHits(Query query, Int32[] results)
in .\src\Test\Search\Spans\TestSpans.cs:line 68
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3SQ(SpanQuery q1,
SpanQuery q2, SpanQuery q3, Int32 slop, Int32[] expectedDocs) in
.\src\Test\Search\Spans\TestSpans.cs:line 75
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3(Int32 slop, Int32[]
expectedDocs) in .\src\Test\Search\Spans\TestSpans.cs:line 80
at Lucene.Net.Search.Spans.TestSpans.TestSpanNearOrdered04() in
.\src\Test\Search\Spans\TestSpans.cs:line 114
(7) Unit Test, TestSpanNearOrdered05, fails:
expected <0>, but was <1>
at Lucene.Net.Search.CheckHits.CheckHits_Renamed(Query query, String
defaultFieldName, Searcher searcher, Int32[] results) in
.\src\Test\Search\CheckHits.cs:line 165
at Lucene.Net.Search.Spans.TestSpans.CheckHits(Query query, Int32[] results)
in .\src\Test\Search\Spans\TestSpans.cs:line 68
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3SQ(SpanQuery q1,
SpanQuery q2, SpanQuery q3, Int32 slop, Int32[] expectedDocs) in
.\src\Test\Search\Spans\TestSpans.cs:line 75
at Lucene.Net.Search.Spans.TestSpans.OrderedSlopTest3(Int32 slop, Int32[]
expectedDocs) in .\src\Test\Search\Spans\TestSpans.cs:line 80
at Lucene.Net.Search.Spans.TestSpans.TestSpanNearOrdered05() in
.\src\Test\Search\Spans\TestSpans.cs:line 120
Most other unit tests pass. The only other failures are all related to
compression support which seems to be the same as others have reported.
Recommendations?
-- Neal
