You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by GitBox <gi...@apache.org> on 2020/09/27 06:03:58 UTC

[GitHub] [lucenenet] NightOwl888 opened a new issue #356: Failing Tests: TestTermVectorsWriter::TestTermVectorCorruption() and TestIndexWriterReader::TestDuringAddIndexes()

NightOwl888 opened a new issue #356:
URL: https://github.com/apache/lucenenet/issues/356


   The following tests are occasionally failing on macOS and Linux (see #269):
   
   1. `Lucene.Net.Index.TestTermVectorsWriter::TestTermVectorCorruption()`
   2. `Lucene.Net.Index.TestIndexWriterReader::TestDuringAddIndexes()`
   
   The failure is due to the fact that the `Lucene.Net.Store.SharingNativeFSLock` keeps a tracking `FileStream` open on the file, but does not specify `FileAccess.Read` on that stream. A second stream is opened in `IsLocked()` to determine whether a lock is held, in this second case `FileAccess.Read` is required to provoke an exception.
   
   Not allowing read access on the tracking stream makes `RAMDirectory` fail when it attempts to copy all of the files in the source directory, which is what is causing each of the above tests to fail.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [lucenenet] NightOwl888 closed issue #356: Failing Tests: TestTermVectorsWriter::TestTermVectorCorruption() and TestIndexWriterReader::TestDuringAddIndexes()

Posted by GitBox <gi...@apache.org>.
NightOwl888 closed issue #356:
URL: https://github.com/apache/lucenenet/issues/356


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org