[JBoss JIRA] (JBIDE-25011) sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25011?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-25011:
----------------------------------
Assignee: Pavol Srna
> sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
> --------------------------------------------------------------------------
>
> Key: JBIDE-25011
> URL: https://issues.jboss.org/browse/JBIDE-25011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.5.x
>
>
> {code}
> 16:49:57 Downloading: http://10.8.243.80:8081/nexus/content/repositories/jboss-nexus-public-jbo...
> 16:49:57
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> 16:49:57 [FATAL] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10
> 16:49:57 @
> 16:49:57 [ERROR] The build could not read 1 project -> [Help 1]
> 16:49:57 [ERROR]
> 16:49:57 [ERROR] The project org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT (/mnt/hudson_workspace/workspace/examples.prcheck/jdk/openjdk-1.8/label/rhel7/jbosstools-central/pom.xml) has 1 error
> 16:49:57 [ERROR] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10: Cannot access ${jbosstools-base-site} with type p2 using the available layout factories: Maven2RepositoryLayoutFactory: Unsupported repository layout p2 -> [Help 2]{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> Is there a reason why these jobs are configured to use 10.8.243.80:8081/nexus instead of simply repository.jboss.org/nexus or origin-repository.jboss.org/nexus ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-25011) sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25011?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25011:
-------------------------------
Fix Version/s: 4.5.x
> sometimes ITests fail to resolve nexus content from 10.8.243.80:8081/nexus
> --------------------------------------------------------------------------
>
> Key: JBIDE-25011
> URL: https://issues.jboss.org/browse/JBIDE-25011
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.5.x
>
>
> {code}
> 16:49:57 Downloading: http://10.8.243.80:8081/nexus/content/repositories/jboss-nexus-public-jbo...
> 16:49:57
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> 16:49:57 [FATAL] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10
> 16:49:57 @
> 16:49:57 [ERROR] The build could not read 1 project -> [Help 1]
> 16:49:57 [ERROR]
> 16:49:57 [ERROR] The project org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT (/mnt/hudson_workspace/workspace/examples.prcheck/jdk/openjdk-1.8/label/rhel7/jbosstools-central/pom.xml) has 1 error
> 16:49:57 [ERROR] Non-resolvable parent POM for org.jboss.tools:central.maven.examples:4.4.3-SNAPSHOT: Could not transfer artifact org.jboss.tools:parent:pom:4.5.1.AM1-SNAPSHOT from/to jbosstools-base (${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 10: Cannot access ${jbosstools-base-site} with type p2 using the available layout factories: Maven2RepositoryLayoutFactory: Unsupported repository layout p2 -> [Help 2]{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> Is there a reason why these jobs are configured to use 10.8.243.80:8081/nexus instead of simply repository.jboss.org/nexus or origin-repository.jboss.org/nexus ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4482) Create 'About' dialog to show most relevant information about installer
by Brian Dellascio (JIRA)
[ https://issues.jboss.org/browse/JBDS-4482?page=com.atlassian.jira.plugin.... ]
Brian Dellascio edited comment on JBDS-4482 at 9/12/17 12:05 PM:
-----------------------------------------------------------------
[~dgolovin], [~crobson] I can mock something up for you.
was (Author: bdellasc):
[~dgolovin][~crobson]I can mock something up for you.
> Create 'About' dialog to show most relevant information about installer
> -----------------------------------------------------------------------
>
> Key: JBDS-4482
> URL: https://issues.jboss.org/browse/JBDS-4482
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.GA
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: New_and_noteworthy, ui
> Fix For: 11.1.0.AM2
>
> Attachments: devsuite-about.png
>
>
> Dialog should contain:
> 1. Application logo, name and version
> 2. Link to documentation
> 3. Link to release notes
> 4. Link to documentation how to report issues
> Dialog can be requested trough context menu 'About' and should show modal dialog with content listed above
> !devsuite-about.png!
> Good Example is Atom editor About Page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4482) Create 'About' dialog to show most relevant information about installer
by Brian Dellascio (JIRA)
[ https://issues.jboss.org/browse/JBDS-4482?page=com.atlassian.jira.plugin.... ]
Brian Dellascio commented on JBDS-4482:
---------------------------------------
[~dgolovin][~crobson]I can mock something up for you.
> Create 'About' dialog to show most relevant information about installer
> -----------------------------------------------------------------------
>
> Key: JBDS-4482
> URL: https://issues.jboss.org/browse/JBDS-4482
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.GA
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: New_and_noteworthy, ui
> Fix For: 11.1.0.AM2
>
> Attachments: devsuite-about.png
>
>
> Dialog should contain:
> 1. Application logo, name and version
> 2. Link to documentation
> 3. Link to release notes
> 4. Link to documentation how to report issues
> Dialog can be requested trough context menu 'About' and should show modal dialog with content listed above
> !devsuite-about.png!
> Good Example is Atom editor About Page.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24938) server.it.weekly jenkins job runs out of disk space on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24938?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24938:
---------------------------------------
And voila! I fixed the HUDSON_STATIC_ENV var on mac and now it works as expected!
{code}
itests jbossqa$ du -sh *
556K org.jboss.tools.as.itests
30M org.jboss.tools.as.management.itests
664K org.jboss.tools.as.ui.bot.itests
20K pom.xml
1.6G target
{code}
> server.it.weekly jenkins job runs out of disk space on Windows
> --------------------------------------------------------------
>
> Key: JBIDE-24938
> URL: https://issues.jboss.org/browse/JBIDE-24938
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.5.1.AM2
>
>
> This job is failing on Windows:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
> It's because it runs out of disk space.
> The windows instances have (I believe) 30GB of disk space. This is set up in our openstack instance by eng-ops:
> https://ci-rhos.centralci.eng.rdu2.redhat.com/dashboard/
> If we wanted more space, we would need to ask eng ops to change this. But it's probably the same for all other users, so I don't think they would change it easily. And in any case, it should be enough.
> The main thing is that we need to reduce the space the tests are using.
> They download all the runtimes via the itests pom:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> The main problem is that this happens 4 times:
> 3.5G ./org.jboss.tools.as.management.itests/target/requirements
> 3.5G ./org.jboss.tools.as.itests/target/requirements
> 3.5G ./target/requirements
> 3.5G ./org.jboss.tools.as.ui.bot.itests/target/requirements
> Fortunately this doesn't mean that all the servers are really downloaded 4 times - they are downloaded once and stored in the local maven download cache. But then the zips are copied over for each of the modules and unzipped.
> So, there are several options:
> a) Get rid of the zips once they're unzipped - that would save half the space. Unfortunately the download plugin does not support this:
> https://github.com/maven-download-plugin/maven-download-plugin
> b) Delete the requirements dir for each module at the end of the maven module lifecycle. This might be doable, needs investigating.
> c) Change the overall setup so that only one download is needed for all the tests - i.e. the child modules don't inherit the download plugin call, but instead use the downloaded runtimes from the higher pom (itests)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24803:
---------------------------------------
Two more things I want to check:
What happens if you download dv 6.2 (that requires path to existing eap 6.4) and you already have it configured in runtime detection?
Variant a): You already have this exact path in 'paths to search for runtimes'
Variant b): It doesn't exactly match the path in 'paths to search', but you already have the eap runtime set up
I will need to check these.
> Add JBoss DV 6.3 to Download Runtimes Wizard
> --------------------------------------------
>
> Key: JBIDE-24803
> URL: https://issues.jboss.org/browse/JBIDE-24803
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard.
> I've also created JDF-867.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24803:
---------------------------------------
It turns out that dv 6.3 contains the whole of eap 6.4 again. So dv 6.1 and 6.3 have eap. Only dv 6.2 doesn't have eap and should behave differently - require path to existing eap 6.4.
> Add JBoss DV 6.3 to Download Runtimes Wizard
> --------------------------------------------
>
> Key: JBIDE-24803
> URL: https://issues.jboss.org/browse/JBIDE-24803
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard.
> I've also created JDF-867.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24964) HUDSON_STATIC_ENV not defined for windows and osx slaves
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24964?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24964:
---------------------------------------
For reference, this is the script that mounts the volume on linux slaves:
https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b...
> HUDSON_STATIC_ENV not defined for windows and osx slaves
> --------------------------------------------------------
>
> Key: JBIDE-24964
> URL: https://issues.jboss.org/browse/JBIDE-24964
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.5.x
>
>
> On windows and osx slaves, HUDSON_STATIC_ENV is not defined. On rhel7 slaves, it's defined as /home/hudson/static_build_env
> Could an equivalent path be set for other OSes, so we can benefit from this NFS-mounted shared space?
> Currently when we run itests on multiple OSes, we see stuff like this, when passing the path to -Ddownload.cache.directory=:
> {code:title=rhel7 - HUDSON_STATIC_ENV = /home/hudson/static_build_env}
> 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
> {code}
> {code:title=win81 - HUDSON_STATIC_ENV not defined}
> 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%%"
> {code}
> {code:title=win10 - HUDSON_STATIC_ENV not defined}
> 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%%"
> {code}
> {code:title=macosx - HUDSON_STATIC_ENV not defined}
> 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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24763:
---------------------------------------
Unfortunately in the next build it all failed on stuff like:
Caused by: java.net.UnknownHostException: download.jboss.org
:(
> 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
>
> Attachments: server-itests.png
>
>
> Here's the job:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> 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)
8 years, 7 months