Hi Everyone, I just completed applying all remaining patches with the exception of "LUCENENET-135 Race condition in DocumentsWriter.UpdateDocument" which I'm still reviewing. I also fixed 3 minor NUnit warning issues.
When I run all the tests, I now get 44 failure of which 31 are due to the fact that I have not setup compression. Assuming compression tests are "good" we have 13 failures to go! Thanks to Doug and DIGY for all your contribution of addressing those port issues. Regards, -- George > -----Original Message----- > From: Digy [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2008 2:22 PM > To: [email protected] > Subject: RE: outstanding issues in SVN head > > Ports and Channels are left open in test cases. Please see > LUCENENET-139 related with > > TestRemoteCachingWrapperFilter.cs > TestRemoteSearchable.cs > TestSort.cs > > DIGY > > -----Original Message----- > From: Doug Sale [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2008 9:11 PM > To: [email protected] > Subject: Re: outstanding issues in SVN head > > I ran through all the tests again after recognizing the issue > with the TestRunner testing harness. (The issue is that the > TestRunner harness maintains a reference to the test class > instance after tests have completed, and thus shared > resources aren't released.) > > The notes I provided regarding these tests failing when run > together in a short period of time: > > - TestRemoteCachingWrapperFilter.cs (all tests) > - TestRemoteSearchable.cs (all tests) > - TestSort.cs (all tests) > > and the note I provided regarding running the following test > multiple times within a short period of time: > > - TestLockFactory.TestNativeFSLockFactoryPrefix() > > are invalid. The failures were the result of using the > TestRunner harness and cannot be replicated using the > standard NUnit harness. > > Doug > TestRemoteSearchable.cs > TestRemoteSearchable.cs > > > > On Thu, Aug 7, 2008 at 11:58 AM, Digy <[EMAIL PROTECTED]> wrote: > > > Hi Doug, > > > > > > > > My current state: > > > > > > > > after applying the simple patches > > > > BooleanScorer2-digy.patch(LUCENENET-128) & > > SupportClass.patch(LUCENENET-135) > > > > to head revision of SVN > > > > > > > > Failing Tests are > > > > > > > > 1- Index: > > > > TestDiverseDocs > > > > TestIOExceptionDuringAbort > > > > TestIOExceptionDuringAbortOnlyOnce > > > > TestStressIndexing (sometimes?) > > > > TestStressIndexing2(both 2 tests) > > > > > > > > > > > > > > > > 2-Search: (after applying LUCENENET-139 patch related with > remoting) > > > > Function/TestCustomScoreQuery.TestCustomScoreFloat > > > > Function/TestCustomScoreQuery.TestCustomScoreShort > > > > Spans/TestSpan.TestSpanNearOrdered02 > > > > Spans/TestSpan.TestSpanNearOrdered03 > > > > Spans/TestSpan.TestSpanNearOrdered04 > > > > Spans/TestSpan.TestSpanNearOrdered05 > > > > > > TestDisjunctionMaxQuery.TestBooleanOptionalWithTiebreaker > > (see LUCENENET-95) > > > > > > > > > > > > > > > > DIGY > > > > > > > > From: Doug Sale [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 07, 2008 12:59 AM > > To: [email protected] > > Subject: outstanding issues in SVN head > > > > > > > > Find attached a listing of outstanding issues in the head > revision of > > the Lucene.Net SVN repo. The document has one source file per line > > and the fields are tab-delimited. There are column-heading > lines for > > each name space (e.g., Lucene.Net.Index.Store). The fields are as > > follows: test class; num tests passed, num tests failed, > num tests not > > run, flag (any failures or not run), name/method of failed tests, > > notes. Additionally, > at > > the bottom of the document are some totals. > > > > This list does not reflect any pending patches. It does contain a > > notes field that might contain salient details (e.g., all the test > > failures that are dependent on a BooleanScorer2 fix). > > > > Digy, George, any others actively developing - please take > a look and > > verify that this is your view of the current state. I will > be using > > this as a guide to focus my efforts and will update the status as > > fixes are committed. > > > > > > Thanks > > > > >
