[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)
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Sun Jun 23 22:26:21 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-14976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-14976:
-------------------------------
Description:
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) we had 2293 tests. Now, for the #82 build, we only have 2139 tests, including the one failure above. This suggests a larger test harness failure somewhere else.
*When you run JavaEE build locally, how many tests are run?*
was:
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) we had 2293 tests. Now, we only have 2139 tests, including the one failure above. This suggests a larger test harness failure somewhere else.
*When you run JavaEE build locally, how many tests are run?*
> 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
>
> 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) we had 2293 tests. Now, for the #82 build, we only have 2139 tests, including the one failure above. This suggests a larger test harness failure somewhere else.
> *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