[jbosstools-issues] [JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

Nick Boldt (JIRA) issues at jboss.org
Fri Sep 1 16:00:00 EDT 2017 

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

Nick Boldt commented on JBIDE-24763:
------------------------------------

Holy crap, we're down to less than 10 failing tests per OS/JDK combination.

This one seems to fail most often, on rhel7, win10, win81, and win7:

{code}
Failed
org.jboss.tools.as.ui.bot.itests.download.InvalidCredentialProductDownloadTest.useInvalidCredentials default (from org.jboss.tools.as.ui.bot.itests.AllTestsSuite)

The following shells remained open [NLS missing message: WizardError in: org.jboss.tools.foundation.ui.internal.messages]

Stacktrace
java.lang.AssertionError: The following shells remained open [NLS missing message: WizardError in: org.jboss.tools.foundation.ui.internal.messages]
	at org.junit.Assert.fail(Assert.java:88)
	at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79)
	at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTest(CloseAllShellsExt.java:71)
	at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:74)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:171)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57){code}

https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=jdk1.8,label_exp=rhel7/testReport/junit/org.jboss.tools.as.ui.bot.itests.download/InvalidCredentialProductDownloadTest/useInvalidCredentials_default/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=jdk1.8,label_exp=win10/testReport/org.jboss.tools.as.ui.bot.itests.download/InvalidCredentialProductDownloadTest/useInvalidCredentials_default/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=openjdk-1.8,label_exp=win10/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=jdk1.8,label_exp=win81/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=openjdk-1.8,label_exp=win81/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=jdk1.8,label_exp=win7/
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/36/jdk=openjdk-1.8,label_exp=win7/

Second most common failures are these, on win10, win81, and win7 (links above):

{code}
org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operate default [1]
org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0]
org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1]
org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1]
org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest default.org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest default
org.jboss.tools.jmx.core.test.DefaultProviderTest.testConnection
{code}

> Some server itests are failing on Jenkins
> -----------------------------------------
>
>                 Key: JBIDE-24763
>                 URL: https://issues.jboss.org/browse/JBIDE-24763
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.5.0.AM2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.5.1.AM2
>
>
> Here's the job:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-server-Run-Unit-and-ITests_master/
> Currently we got around 30 failures:
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
>  org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1]	5.3 sec	1
>  org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7]	76 ms	1
>  org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0]	17 sec	1
>  org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4]	1.7 sec	2
>  org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4]	5.3 sec	2
>  org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1]	2.3 sec	3
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0]	4.4 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3]	2.2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7]	2.3 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8]	2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11]	2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12]	2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13]	2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14]	2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15]	2.1 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16]	2 sec	6
>  org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17]	2 sec	6
>  org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0]	1.7 sec	6
>  org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0]	1 min 49 sec	6
>  org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1]	1 min 43 sec	6
>  org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName	2.6 sec	6
>  org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection	0.13 sec	6
>  org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2]	1.7 sec	7
> {code}
> Nick already shared some details in JBIDE-22799



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

More information about the jbosstools-issues mailing list