You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucenenet.apache.org by "Digy (JIRA)" <ji...@apache.org> on 2009/11/16 19:25:39 UTC

[jira] Resolved: (LUCENENET-262) Lucene.Net.Index.TestSegmentReader + Lucene.Net.Index.TestNorms + Lucene.Net.Index.TestMultiReader

     [ https://issues.apache.org/jira/browse/LUCENENET-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Digy resolved LUCENENET-262.
----------------------------

    Resolution: Fixed

I just added a TearDown to TestSegmentReader
{code}
        [TearDown]
        public void TearDown()
        {
            dir = new RAMDirectory();
		    testDoc = new Document();
        }
{code}

and committed

> Lucene.Net.Index.TestSegmentReader +  Lucene.Net.Index.TestNorms + Lucene.Net.Index.TestMultiReader
> ---------------------------------------------------------------------------------------------------
>
>                 Key: LUCENENET-262
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-262
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Iliev Andrei
>         Attachments: TestMultiReader.patch, TestNorms.patch, TestSegmentReader.patch
>
>
> 1) Resolving 'No suitable constructor was found' error
> 2) Same objects used across tests (but should be recreated)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.