[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4077 at 10/24/16 12:07 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|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... 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? -- This message was sent by Atlassian JIRA (v6.4.11#64026)