[jbosstools-issues] [JBoss JIRA] (JBIDE-13097) test failure in org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests)

[Viacheslav Kabanovich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735485#comment-12735485 ] 

Viacheslav Kabanovich edited comment on JBIDE-13097 at 11/19/12 3:52 PM:
-------------------------------------------------------------------------

I believe that it is not a regression, but an existing drawback that produced a very low probability of failure. Operations on variable Z.counter were not synchronized. I could not reproduce exactly this problem, but by increasing TREAD_NUMBER (number of threads) I was able to hang tests - hanging is explained by Z.counter remaining greater than 0, while error in this issue may be explained by Z.counter reduced to 0 faster than in correct handling. It would seem that these two error cases are equally probable, but in my case I got only hanging.
                
      was (Author: scabanovich):
    I believe that it is not a regression, but an existing drawback that produced a very low probability of failure. Operations on variable Z.counter were not synchronized. I could not reproduce exactly this problem, but by increasing TREAD_NUMBER (number of threads) I was able to hang tests - hanging is explained by Z.counter remaining greater than 0, while error in this issue may be explained by Z.counter reduced to 0 faster than in correct handling. It would seem that this two error cases are equally probable, but in my case I got only hanging.
                  
> test failure in org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests) 
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13097
>                 URL: https://issues.jboss.org/browse/JBIDE-13097
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common/jst/core
>    Affects Versions: 4.0.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Viacheslav Kabanovich
>            Priority: Blocker
>             Fix For: 4.0.0.CR1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--base/lastCompletedBuild/testReport/org.jboss.tools.common.el.core.test/ELParserTest/testMultiThreadAccess/}
> Regression
> org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests)
> Failing for the past 1 build (Since Unstable#31 )
> Error Message: expected:<9990> but was:<9989>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<9990> but was:<9989>
> 	at junit.framework.Assert.fail(Assert.java:50)
> 	at junit.framework.Assert.failNotEquals(Assert.java:287)
> 	at junit.framework.Assert.assertEquals(Assert.java:67)
> 	at junit.framework.Assert.assertEquals(Assert.java:199)
> 	at junit.framework.Assert.assertEquals(Assert.java:205)
> 	at org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess(ELParserTest.java:429)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira