[ 
https://issues.apache.org/jira/browse/LUCENE-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926605#action_12926605
 ] 

Uwe Schindler edited comment on LUCENE-2730 at 10/30/10 12:38 PM:
------------------------------------------------------------------

Hangs in this and other tests can also come from incorrect test MT programming. 
Just think about Michael Busch's talk @ LuceneRev. The test uses some fields in 
the thread that are not volatile or synchronized on. The test is fixed in 
trunk/3.x during our total test overhaul. There are about 10 tests using the 
same wrong thread inner class.

If we want to fix that we must also fix backwards... happy tag creating again 
*g*

      was (Author: thetaphi):
    Hangs in this and other tests can also come from increet test MT 
programming. Just think about Michael Busch's talk @ LuceneRev. The test uses 
some fields in the thread that are not volatile or synchronized on. The test is 
fixed in trunk/3.x during our total test overhaul. There are about 10 tests 
using the same wrong thread inner class.

If we want to fix that we must also fix backwards... happy tag creating again 
*g*
  
> intermittent deadlock in TestAtomicUpdate,TestIndexWriterExceptions
> -------------------------------------------------------------------
>
>                 Key: LUCENE-2730
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2730
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.9.3, 3.0.2
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9.4, 3.0.3
>
>         Attachments: LUCENE-2730.patch
>
>
> While backporting issues for 2.9.x/3.0.x release I hit deadlocks in these two 
> tests, under both test-core and test-tag.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to