[jbosstools-issues] [JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)

[Alexey Kazakov (JIRA)]

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

Alexey Kazakov commented on JBIDE-13460:
----------------------------------------

Victor, please take a look at these two tests.

Nick, Seam tests (and other javaee tests) should not take so long time. If it takes more then 8hrs then they just hung. But there are so many tests... Can we see what test took so long time?
                
> test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13460
>                 URL: https://issues.jboss.org/browse/JBIDE-13460
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JSF, Seam 2
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Victor Kukharchuk
>             Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/}
> Test Result
> 2 failures (-7)
> 2,118 tests (-171)
> Took 53 min.
> add description
> All Failed Tests
> Test Name   	Duration   	Age   
> >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 	36 sec	4
> >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 	0.19 sec	25
> {code}
> Note that we've had considerably more tests complete in the past:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/238/ (Jan 14, 2383 tests, 1 failure)
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/226/ (Jan 10, 2383 tests, 0 failure)

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