[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4077:
----------------------------------
{code}
[/qa/tools/opt/x86_64/jdk1.8.0_102/jre/bin/java, -Dosgi.noShutdown=false, -Dosgi.os=linux, -Dosgi.ws=gtk, -Dosgi.arch=x86_64, -javaagent:/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/.repository/org/jacoco/org.jacoco.agent/0.7.1.201405082137/org.jacoco.agent-0.7.1.201405082137-runtime.jar=destfile=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/target/jacoco.exec,append=true,includes=org.jboss.tools.*, -Xms512m, -Xmx1024m, -XX:PermSize=256m, -XX:MaxPermSize=384m, -Dswt.bot.test.record.screencast=false, -Dorg.eclipse.swtbot.screenshots.dir=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/screenshots, -Dusage_reporting_enabled=false, -Dcom.atlassian.connector.eclipse.monitor.usage.first.time=false, -Dcom.atlassian.connector.eclipse.monitor.usage.enabled=false, -Dreddeer.close.shells=true, -Dreddeer.close.welcome.screen=true, -Dreddeer.disable.maven.download.repo.index.on.startup=true, -Drd.config=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/classes/project, -Dreq.java.version=1.8, -Dreq.java.home=/qa/tools/opt/amd64/jdk1.8.0_last, -Djbosstools.test.jboss-as-3.2.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-3.2.8.SP1, -Djbosstools.test.jboss-as-4.0.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-4.0.5.GA, -Djbosstools.test.jboss-as-4.2.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-4.2.3.GA, -Djbosstools.test.jboss-as-5.0.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-5.0.1.GA, -Djbosstools.test.jboss-as-5.1.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-5.1.0.GA, -Djbosstools.test.jboss-as-6.x.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-6.1.0.Final, -Djbosstools.test.jboss-as-7.0.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-as-7.0.2.Final, -Djbosstools.test.jboss-as-7.1.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-as-7.1.1.Final, -Djbosstools.test.jboss-wildfly-8.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/wildfly-8.2.0.Final, -Djbosstools.test.jboss-wildfly-9.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/wildfly-9.0.1.Final, -Djbosstools.test.jboss-wildfly-10.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/wildfly-10.0.0.CR2, -Djbosstools.test.jboss-eap-4.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-eap-4.3/jboss-as, -Djbosstools.test.jboss-eap-5.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-eap-5.2/jboss-as, -Djbosstools.test.jboss-eap-6.0.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-eap-6.0, -Djbosstools.test.jboss-eap-6.x.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-eap-6.4, -Djbosstools.test.jboss-eap-7.x.home=/mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/requirements/jboss-eap-7.0, -Dusage_reporting_enabled=false, -Dorg.jboss.tools.tests.skipPrivateRequirements=false, -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true, -Dosgi.clean=true, -Dorg.eclipse.update.reconcile=false, -jar, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.200.v20160318-1642/org.eclipse.equinox.launcher-1.3.200.v20160318-1642.jar, -data, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/work/data, -install, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/devstudio-10.2.0.AM2-v20161017-2256-B6218-installer-standalone, -configuration, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/devstudio-10.2.0.AM2-v20161017-2256-B6218-installer-standalone/configuration, -application, org.eclipse.tycho.surefire.osgibooter.uitest, -testproperties, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/surefire.properties, -product, com.jboss.devstudio.core.product, -nouithread, -pluginCustomization, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/../pluginCustomization.ini]{code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Inst...
Appears to be working. I'm seeing these properties:
* -data, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/work/data,
* -install, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/devstudio-10.2.0.AM2-v20161017-2256-B6218-installer-standalone,
* -configuration, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/devstudio-10.2.0.AM2-v20161017-2256-B6218-installer-standalone/configuration,
* -application, org.eclipse.tycho.surefire.osgibooter.uitest,
* -testproperties, /mnt/hudson_workspace/workspace/jbosstools-integration-tests.aggregate_master/sources/tests/org.jboss.ide.eclipse.as.ui.bot.test/target/surefire.properties,
* -product, com.jboss.devstudio.core.product
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Marián Labuda
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4077 at 10/17/16 7:37 PM:
------------------------------------------------------------
Three ideas:
a) we need to enable the -Pinstall-base profile so that the work folder is set to the devstudio install folder
b) we need to actually pass test.installBase into surefire via this patch (which I haven't tested yet): https://github.com/jbosstools/jbosstools-integration-tests/pull/1639
c) a+b
Please note that testing is not my core expertise so if I can't solve this you might need to call in someone else, like Mickael Istria.
Seems the basic problem, however, is that surefire is not being invoked against the correct devstudio install folder. So, if we can figure out how to make that happen, your tests should be better.
was (Author: nickboldt):
Three ideas:
a) we need to enable the -Pinstall-base profile so that the work folder is set to the devstudio install folder
b) we need to actually pass test.installBase into surefire via this patch (which I haven't tested yet): https://github.com/jbosstools/jbosstools-integration-tests/pull/1639
c) a+b
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Marián Labuda
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4077:
----------------------------------
Three ideas:
a) we need to enable the -Pinstall-base profile so that the work folder is set to the devstudio install folder
b) we need to actually pass test.installBase into surefire via this patch (which I haven't tested yet): https://github.com/jbosstools/jbosstools-integration-tests/pull/1639
c) a+b
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Marián Labuda
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny updated ERT-177:
--------------------------------
Labels: General bzira (was: 3.8_RC1 General bzira)
> Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-177
> URL: https://issues.jboss.org/browse/ERT-177
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: General, bzira
> Fix For: Neon.2 (4.6)
>
>
> Created attachment 261462
> Selection related errors
> See the screenshot attached for illustration.
> Steps for reproduce:
> - Create a javascript file with a function and a call to that function.
> - Try to invoke content assist: FAIL: no new function appears in CA proposals
> - Save, close and open the file again.
> - Try to invoke content assist: Now the new function appears in CA proposals
> - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration
> - FAIL: See wrong text regions highlighted.
> - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny resolved ERT-177.
---------------------------------
Resolution: Done
> Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-177
> URL: https://issues.jboss.org/browse/ERT-177
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: General, bzira
> Fix For: Neon.2 (4.6)
>
>
> Created attachment 261462
> Selection related errors
> See the screenshot attached for illustration.
> Steps for reproduce:
> - Create a javascript file with a function and a call to that function.
> - Try to invoke content assist: FAIL: no new function appears in CA proposals
> - Save, close and open the file again.
> - Try to invoke content assist: Now the new function appears in CA proposals
> - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration
> - FAIL: See wrong text regions highlighted.
> - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23351) Deploy Docker Wizard: Image stream sometimes is not created for local docker images
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23351?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23351:
---------------------------------------
[~adietish] See DeployImageJob and CreateApplicationFromImageJob. It looks like if you are deploying a docker image the imagestream is always created where if you are deploying from a template there are some conditionals in place, one of which is to check if openshift will be able to pull the desired image, and to skip generation if not.
> Deploy Docker Wizard: Image stream sometimes is not created for local docker images
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23351
> URL: https://issues.jboss.org/browse/JBIDE-23351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Attachments: is_not_created.png
>
>
> When deploying a local image to OpenShift, Image stream is not created even an image has been pushed to registry. For images on docker hub it works ok.
> Following message is shown in resource summary:
> !is_not_created.png!
> I had checked the checkbox to push to registry. But I am not able to reproduce this all the time. I was able to do it only 2 times.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months