[jbosstools-issues] [JBoss JIRA] (JBIDE-14976) Regression / test failure in org.jboss.tools.cdi.core.test.TypeTest.testType (from org.jboss.tools.cdi.core.test.CDICoreAllTests)

Viacheslav Kabanovich (JIRA) jira-events at lists.jboss.org
Mon Jun 24 19:46:20 EDT 2013


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

Viacheslav Kabanovich commented on JBIDE-14976:
-----------------------------------------------

In trying to reproduce this failure, I found one possible cause: Cache for types may return obsolete IType objects. When testType() is called several times, reimporting test project resulted in obsolete types lingering in the cache. However, project TypeTest was used by this test only, and was imported just one time. 
So, now I suggest a partial fix: preventing cache from returning obsolete types and adding more methods that test types.
                
> Regression / test failure in org.jboss.tools.cdi.core.test.TypeTest.testType (from org.jboss.tools.cdi.core.test.CDICoreAllTests) 
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14976
>                 URL: https://issues.jboss.org/browse/JBIDE-14976
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: CDI
>    Affects Versions: 4.1.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Viacheslav Kabanovich
>             Fix For: 4.1.0.CR1
>
>
> After switching the JavaEE build to run on RHEL6 only, I managed to get a clean build, but there's one test failure now:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/82/}
> Regression
> org.jboss.tools.cdi.core.test.TypeTest.testType (from org.jboss.tools.cdi.core.test.CDICoreAllTests)
> Failing for the past 1 build (Since Unstable#82 )
> Took 4.3 sec.
> add description
> Error Message
> expected:<11> but was:<10>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<11> but was:<10>
> {code}
> Note too that for the #32 build (using 4.30.5.Alpha-SNAPSHOT TP, on Mar 6) we had 2293 tests. Now, for the #82 build (using 4.30.5.Alpha6-SNAPSHOT TP, on Jun 23), we have only 2139 tests, including the one failure above. This suggests a larger test harness failure somewhere else, or that a number of tests have been removed? 
> *When you run JavaEE build locally, how many tests are run?*

--
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


More information about the jbosstools-issues mailing list