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

[Fred Bricon]

For the maven component,

- local svn up, mvn clean install => builds without errors
- In the maven component build 258, all tests passed, but the build 
failed because it 404'ed. Also a call to 
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--maven/258/api/xml?xpath=//lastBuiltRevision 
returns

XPath //lastBuiltRevision didn't match

Dunno how bad it is.
- latest maven component build failed because nexus 503'ed :

Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL:https://repository.jboss.org/nexus/content/groups/developer/org/apache/maven/maven-error-diagnostics/2.0.6/maven-error-diagnostics-2.0.6.pom

- full tests build 
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/677/ 
all maven tests pass

So, all in all, we can say tests pass (yay!), but the build is still 
brittle.

regards,

Fred Bricon


On 06/14/2011 01:56 AM, Nick Boldt 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/jbosstools-3.3_trunk.component--cdi/345/console 
>
>
> 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/test/ 
>
>
> == JSF ==
>
> 1 or 2 test failures since June 9:
>
> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf/271/testReport/ 
>
>
> http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jsf/272/testReport/ 
>
>
> == 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/jbosstools-3.3_trunk.component--maven/changes 
>
>
> 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/jbosstools-3.3_trunk.component--seam/350/testReport/ 
>
>
> == WS ==
>
> 4 test failures, 1 missing (down from 180 tests to 179).
>
> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--ws/lastCompletedBuild/testReport/ 
>
>
> == 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.
>
> 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.
>