August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24940) Forge: refactor integration tests for use with RedDeer 2.0

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24940: ------------------------------------- Summary: Forge: refactor integration tests for use with RedDeer 2.0 Key: JBIDE-24940 URL: https://issues.jboss.org/browse/JBIDE-24940 Project: Tools (JBoss Tools) Issue Type: Task Components: forge, integration-tests Affects Versions: 4.5.1.AM1 Reporter: Josef Kopriva -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[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 resolved JBIDE-24938. ----------------------------------- Fix Version/s: 4.5.1.AM2 Resolution: Done Done in JBIDE-24763 by Nick. It's worth checking later that it actually works as expected. > 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

1
0
0 / 0

[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: --------------------------------------- I was about to tackle the space problem [here|JBIDE-24938] but you were faster! > 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/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

1
0
0 / 0

[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: --------------------------------------- OK, seems like Nick beat us to it in JBIDE-24763: {quote} This PR should do 3 things: a) reduce on-disk footprint from 4 x 3.5G to 1 x 3.5G for the downloaded AS/WF/EAP runtimes, by reusing itests/target/requirements/ folder (rather than itests/target/requirements + 3 x itests/*/target/requirements/ folders) b) prevent downloading the above runtimes when running the itests/pom.xml; instead downloads (or recycling from ~/.m2) will be done during the specific itests/*/pom.xml plugins, so we don't have to prefetch everything before starting the first plugin c) clean the itests/target/requirements folder before fetching (or copying from local) runtimes, to ensure the folder is clean and ready for use before each test plugin run https://github.com/jbosstools/jbosstools-server/pull/534 {quote} > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24797: ------------------------------------- Comment: was deleted (was: it looks like the maven plugin at https://github.com/revelc/formatter-maven-plugin can read eclipse formatter files, allowing us to share the settings btw. the IDE and the build where we can enforce them. Didn't test it yet though. [~dbocharov], [~jeffmaury], [~rob.stryker] Thoughts?) > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.AM2 > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24797: ------------------------------------------ it looks like the maven plugin at https://github.com/revelc/formatter-maven-plugin can read eclipse formatter files, allowing us to share the settings btw. the IDE and the build where we can enforce them. Didn't test it yet though. [~dbocharov], [~jeffmaury], [~rob.stryker] Thoughts? > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.AM2 > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24222: ------------------------------------------ [~rob.stryker] [~mmalina] sounds like great news! > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: help_wanted > Fix For: 4.5.1.AM2 > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png, server-adapter-error.tiff > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19811) Refactor IConnection interface to support connection specific display formating

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19811?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19811: ------------------------------------- Fix Version/s: LATER (was: 4.5.x) > Refactor IConnection interface to support connection specific display formating > ------------------------------------------------------------------------------- > > Key: JBIDE-19811 > URL: https://issues.jboss.org/browse/JBIDE-19811 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Labels: connection, openshift_v3 > Fix For: LATER > > > Ultimately, IConnection should be oblivious to username and password since those are authentication specific. There are a few places where we should introduce a 'display' interface which each type can implement in order to remove the dependency of the common label provider on username and password -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Refactoring: get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19715 at 8/29/17 5:17 PM: ------------------------------------------------------------- Fixed: https://github.com/jbosstools/jbosstools-build-sites/commit/66bf509d7cc9a... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (rebuilding, problem in job config) * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Checked for same artifacts: * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_03-42-51-B1688 vs. __) *pending* * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_21-05-06-B973 vs. 2017-08-29_15-16-39-B979) * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_06-49-10-B969 vs. 2017-08-29_11-18-11-B978) * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_07-00-18-B1473 vs. 2017-08-29_20-56-36-B1485) was (Author: nickboldt): Fixed: https://github.com/jbosstools/jbosstools-build-sites/commit/66bf509d7cc9a... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (rebuilding, problem in job config) * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Checked for same artifacts: * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_03-42-51-B1688 vs. __) *pending* * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_21-05-06-B973 vs. 2017-08-29_15-16-39-B979) * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_06-49-10-B969 vs. 2017-08-29_11-18-11-B978) * http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b... (2017-08-28_07-00-18-B1473 vs. 2017-08-29_17-32-31-B1484) > Refactoring: get rid of "fullSite", stick with "repository" > ----------------------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.1.AM2 > > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24763 at 8/29/17 4:38 PM: ------------------------------------------------------------- This PR should do 3 things: a) reduce on-disk footprint from 4 x 3.5G to 1 x 3.5G for the downloaded AS/WF/EAP runtimes, by reusing itests/target/requirements/ folder (rather than itests/target/requirements + 3 x itests/*/target/requirements/ folders) b) prevent downloading the above runtimes when running the itests/pom.xml; instead downloads (or recycling from ~/.m2) will be done during the specific itests/*/pom.xml plugins, so we don't have to prefetch everything before starting the first plugin c) clean the itests/target/requirements folder before fetching (or copying from local) runtimes, to ensure the folder is clean and ready for use before each test plugin run https://github.com/jbosstools/jbosstools-server/pull/534 was (Author: nickboldt): This PR should do two things: a) reduce on-disk footprint from 4 x 3.5G to 1 x 3.5G for the downloaded AS/WF/EAP runtimes, by reusing itests/target/requirements/ folder (rather than itests/target/requirements + 3 x itests/*/target/requirements/ folders) b) prevent downloading the above runtimes when running the itests/pom.xml; instead downloads (or recycling from ~/.m2) will be done during the specific itests/*/pom.xml plugins, so we don't have to prefetch everything before starting the first plugin https://github.com/jbosstools/jbosstools-server/pull/533 > 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/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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017