You're welcome.

By the way, the TestInsanity1 test could be forced to fail on every run by 
inserting a GC.Collect() call just before the CheckInsanity call.
I didn't patch the TestCase itself since it's ported from java code...

Luc

-----Original Message-----
From: Christopher Currens (JIRA) [mailto:j...@apache.org] 
Sent: donderdag 31 mei 2012 18:14
To: lucene-net-dev@lucene.apache.org
Subject: [jira] [Commented] (LUCENENET-484) Some possibly major tests 
intermittently fail


    [ 
https://issues.apache.org/jira/browse/LUCENENET-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286699#comment-13286699
 ] 

Christopher Currens commented on LUCENENET-484:
-----------------------------------------------

Thanks Luc.  This is great stuff.  I'll run the patch on my local box and 
double check everything.  Your help with this is appreciated by all of us!
                
> Some possibly major tests intermittently fail
> ----------------------------------------------
>
>                 Key: LUCENENET-484
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-484
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core, Lucene.Net Test
>    Affects Versions: Lucene.Net 3.0.3
>            Reporter: Christopher Currens
>             Fix For: Lucene.Net 3.0.3
>
>         Attachments: Lucenenet-484-WeakDictionary.patch, 
> Lucenenet-484-WeakDictionaryTests.patch
>
>
> These tests will fail intermittently in Debug or Release mode, in the core 
> test suite:
> # -Lucene.Net.Index:-
> #- -TestConcurrentMergeScheduler.TestFlushExceptions-
> # Lucene.Net.Store:
> #- TestLockFactory.TestStressLocks
> # Lucene.Net.Search:
> #- TestSort.TestParallelMultiSort
> # Lucene.Net.Util:
> #- TestFieldCacheSanityChecker.TestInsanity1
> #- TestFieldCacheSanityChecker.TestInsanity2
> #- (It's possible all of the insanity tests fail at one point or 
> another) # Lucene.Net.Support
> #- TestWeakHashTableMultiThreadAccess.Test
> TestWeakHashTableMultiThreadAccess should be fine to remove along with the 
> WeakHashTable in the Support namespace, since it's been replaced with 
> WeakDictionary.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to