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

Posted to dev@lucenenet.apache.org by "Doug Sale (JIRA)" <ji...@apache.org> on 2008/07/17 16:01:31 UTC

[jira] Updated: (LUCENENET-131) bugs in TestIndexWriter test cases

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

Doug Sale updated LUCENENET-131:
--------------------------------

    Attachment: TestIndexWriter.patch

fix for test cases in TestIndexWriter:

Lucene.Net.Index.TestIndexWriter.TestDocumentsWriterAbort
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringAbort
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringAbortOnlyOnce
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringAbortWithThreads
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringAbortWithThreadsOnlyOnce
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringCloseDocStore
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringCloseDocStoreOnlyOnce
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringCloseDocStoreWithThreads
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringCloseDocStoreWithThreadsOnlyOnce
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringWriteSegment
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringWriteSegmentOnlyOnce
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringWriteSegmentWithThreads
Lucene.Net.Index.TestIndexWriter.TestIOExceptionDuringWriteSegmentWithThreadsOnlyOnce

> bugs in TestIndexWriter test cases
> ----------------------------------
>
>                 Key: LUCENENET-131
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-131
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Doug Sale
>            Priority: Minor
>         Attachments: TestIndexWriter.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Certain test cases introspect the call stack to determine when to simulate an I/O exception.  This code was not converted properly from the Java version.
> Specifically, it attemtped to use the StackTrace property of System.Exception, rather than the System.Diagnostics facilities.

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