lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy" <digyd...@gmail.com>
Subject RE: outstanding issues in SVN head
Date Thu, 07 Aug 2008 16:58:09 GMT
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:dougsale@gmail.com] 
Sent: Thursday, August 07, 2008 12:59 AM
To: lucene-net-dev@incubator.apache.org
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


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message