[jbosstools-issues] [JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-4077 at 10/24/16 12:08 PM:
-------------------------------------------------------------

So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing. 

Good vs. bad: 
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM1/2/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ConfigPropertyAnnotationTest.testInjectUnsupportedConfigProperty.png vs. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM2/1/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ExceptionHandlerAnnotationTest@ServerRequirement.png

This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading. 

Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave.  Can we start devstudio with {code}
-debug -console -consolelog{code} to get more details about what's (not) happening?

Or, can someone run these tests locally and debug them in Eclipse?

http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html



was (Author: nickboldt):
So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing. 

Good vs. bad: 
!https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM1/2/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ConfigPropertyAnnotationTest.testInjectUnsupportedConfigProperty.png|thumbnail! !https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM2/1/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ExceptionHandlerAnnotationTest@ServerRequirement.png|thumbnail!

This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading. 

Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave.  Can we start devstudio with {code}
-debug -console -consolelog{code} to get more details about what's (not) happening?

Or, can someone run these tests locally and debug them in Eclipse?

http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html


> 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: Nick Boldt
>            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)