lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Currens (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENENET-484) Some possibly major tests intermittently fail
Date Fri, 13 Apr 2012 20:51:17 GMT

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

Christopher Currens updated LUCENENET-484:
------------------------------------------

    Description: 
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.

  was:
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.


So, I figured out the issue with the ConcurrentMergeScheduler, it was simply a port issue
for the actual Test.  I had to add a workaround in {{FailOnlyOnFlush.Eval(Directory)}}, since
java would compare stack frame with "main" (the thread running the test, it seems), and only
execute the code if that was the case.  That doesn't exactly work in .NET code, so instead,
I inverted the check too look for the thread name not containing "Merge Thread".  I can no
longer reproduce it at all, where I could before every time.
                
> 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
>
>
> 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

        

Mime
View raw message