Re: [jbosstools-dev] JBT 3.3.0.M2 status -- test failures in CDI, JSF, Maven, Seam, WS, VPE, Struts

Only hudson config change was to reorg the workflow, as discussed @ F2F. == BEFORE == 1. mvn clean install -f ~/trunk/vpe/pom.xml (if tests or compilation fails, do not publish; downstream aggregation BLOCKED by failure) 2. publish.sh == AFTER == 1. mvn clean install -f ~/trunk/vpe/pom.xml -Dmaven.test.skip (if compilation fails, do not publish) 2. publish.sh 3. mvn clean test osgi-test:test -f ~/trunk/vpe/tests/pom.xml (build can be red due to failing tests, but bits will still be published and aggregated) --- If somehow that change is what's causing some tests to not be run (or to fail utterly?), then the fault may be mine. I could run the vpe/pom.xml instead of the vpe/tests/pom.xml if that'd help...? Nick On 06/14/2011 08:05 AM, Max Rydahl Andersen wrote: > > There are two kinds of removed tests: >> 1. All VPE tests are vanished from jbosstools-3.3_trunk.tests job. I (as >> well as Nick) do not know the reason why they are vanished. But I guess that >> somebody removed them from the job to make it stable. >> > > *somebody* ? who would that be and how are they removed ? > > I dont think anyone would remove such things without letting the dev team > know about. > > Is this a pure hudson configuration change or something in SVN ? > > /max > > 2. The quantity of VPE JUnit tests is decreased from 219 to 192. I did it >> myself in the scope of JBIDE-8487 (Decrease quantity of junit tests). >> >> --Yahor >> >> On Tue, Jun 14, 2011 at 1:35 PM, Denis Golovin<dgolovin(a)exadel.com> >> wrote: >> What tests were removed and why? >> >> Denis >> >> Regarding VPE, >>> >>> On Tue, Jun 14, 2011 at 2:56 AM, Nick Boldt<nboldt(a)redhat.com> wrote: >>> >>> Six (6) components are having some problems today. Here's the list! >>>> >>>> ---------------- >>>> >>>> == CDI == >>>> >>>> Many test failures (55?) in these suites: >>>> >>>> org.jboss.tools.cdi.text.ext.test >>>> org.jboss.tools.cdi.ui.test >>>> org.jboss.tools.cdi.seam.config.ui.test >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... >>>> >>>> Also, count of tests is down from 454 to 399 (55 tests failing to >>>> report >>>> results) since June 9. >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--cdi... >>>> >>>> == JSF == >>>> >>>> 1 or 2 test failures since June 9: >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf... >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf... >>>> >>>> == Maven == >>>> >>>> June 10, we had 6 passing tests. 10hrs later, we're down to ZERO >>>> passing >>>> tests. >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... >>>> >>>> Could this be due to me moving up to a newer version of m2e? >>>> >>>> http://source.jboss.org/changelog/JBossTools/?cs=32015 >>>> >>>> == Seam == >>>> >>>> 6 test failures in org.jboss.tools.seam.ui.test, and duplicate spins of >>>> the >>>> same tests (?): >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... >>>> >>>> == WS == >>>> >>>> 4 test failures, 1 missing (down from 180 tests to 179). >>>> >>>> >>>> >>>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... >>>> >>>> == VPE / Overall All-in-One test suite == >>>> >>>> The all-in-one test builder is reporting that nearly 800 tests are >>>> missing >>>> since Friday - from 3239 tests in build #673 to 2441 in build #676! >>>> >>>> Here are the test suites that vanished from the #673 build and are no >>>> longer present in the #676 build - looks like it's all VPE-related >>>> tests >>>> that have vanished. >>>> >>>> Did somebody disable them in this job because of >>> https://issues.jboss.org/browse/JBIDE-8777 (RHEL5 x64& VPE issue)? >>> >>> >>>> Package Duration Fail (diff) Skip (diff) Total (diff) >>>> org.jboss.tools.jsf.vpe.ajax4jsf.test 47 sec 0 0 >>>> 24 >>>> org.jboss.tools.jsf.vpe.facelets.test 47 sec 0 0 >>>> 14 >>>> org.jboss.tools.jsf.vpe.jbpm.test 20 sec 0 0 >>>> 4 >>>> org.jboss.tools.jsf.vpe.jsf.test 9 min 25 sec 0 >>>> 0 >>>> 224 >>>> org.jboss.tools.jsf.vpe.jstl.test 1 min 13 sec 0 >>>> 0 >>>> 42 >>>> org.jboss.tools.jsf.vpe.myfaces.test 1 min 19 sec 0 >>>> 0 >>>> 43 >>>> org.jboss.tools.jsf.vpe.richfaces.test 2 min 39 sec 0 >>>> 0 >>>> 115 >>>> org.jboss.tools.jsf.vpe.seam.test 1 min 38 sec 0 >>>> 0 >>>> 65 >>>> >>>> org.jboss.tools.struts.vpe.struts.test 1 min 24 sec 0 >>>> 0 >>>> 89 >>>> >>>> org.jboss.tools.vpe.html.test 2 min 4 sec 0 0 >>>> 111 >>>> org.jboss.tools.vpe.jsp.test 43 sec 0 0 >>>> 23 >>>> >>>> org.jboss.tools.vpe.spring.test 55 sec 0 0 >>>> 27 >>>> org.jboss.tools.vpe.ui.test 38 sec 0 0 >>>> 12 >>>> >>>> org.jboss.tools.vpe.xulrunner.test 2.6 sec 0 0 >>>> 7 >>>> >>>> Note that the VPE job itself is down from 219 tests to 192, suggesting >>>> similar (or more?) test failures there too. >>>> >>>> 219 to 192 is OK, we removed a part of VPE tests intentionally. >>> >>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools& Dev Studio >>>> http://nick.divbyzero.com >>>> >>>> >>>> >>> >> >> > /max > http://about.me/maxandersen > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com