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

Nick Boldt (JIRA) issues at jboss.org
Wed Aug 30 12:29:00 EDT 2017 

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

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

Latest params for the job [1] for 4 OSes:

[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.it.weekly/jdk=openjdk-1.8,label_exp=win81/24/consoleFull

{code}
16:05:51 [win81] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings7229513778735293013.xml -Djdk=openjdk-1.8 -Dlabel_exp=win81 -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win81" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false 
-Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000 
-Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last 
-Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last 
-Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last 
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum" 
-DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"

16:05:48 [win10] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings8339429706904285132.xml -Djdk=openjdk-1.8 -Dlabel_exp=win10 -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win10" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false 
-Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000 
-Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last 
-Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last 
-Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last 
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum" 
-DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"

16:05:48 [rhel7] $ /mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /tmp/settings2086504014812240990.xml -Djdk=openjdk-1.8 -Dlabel_exp=rhel7 -Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=rhel7 -DBUILD_NUMBER=24 -DskipPrivateRequirements=false 
-Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dsurefire.itests.timeout=10000 
-Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last 
-Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last 
-Djbosstools.test.jre.5=/qa/tools/opt/x86_64/jdk1.5.0_last 
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum 
-DjgitDirtyWorkingTree=warning

16:05:46 [macosx] $ /jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /var/folders/tp/hcfshtz152n2t8y4jfl08w140000gp/T/settings6780477723089804684.xml -Djdk=jdk1.8 -Dlabel_exp=macosx -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=jdk1.8,label_exp=macosx -DBUILD_NUMBER=24 -DskipPrivateRequirements=false 
-Djbosstools.test.jre.8=/qa/tools/opt/osx/jdk1.8.0_last -Dsurefire.itests.timeout=10000 
-Djbosstools.test.jre.7=/qa/tools/opt/osx/jdk1.7.0_last 
-Djbosstools.test.jre.6=/qa/tools/opt/osx/jdk1.8.0_last 
-Djbosstools.test.jre.5=/qa/tools/opt/osx/jdk1.8.0_last 
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum 
-DjgitDirtyWorkingTree=warning
{code}

So... looks like none of the tests are actually using openjdk right now for the jre.* parameters, even if the BUILDS are running w/ openJDK 8

> 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