[JBoss JIRA] (JBIDE-24188) CDKv3 terminal output in IDE is ugly when using hyperv
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24188?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24188:
-------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.x)
> CDKv3 terminal output in IDE is ugly when using hyperv
> ------------------------------------------------------
>
> Key: JBIDE-24188
> URL: https://issues.jboss.org/browse/JBIDE-24188
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Environment: Windows 10, x86_64, hyper V.
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM2
>
> Attachments: Terminal-HyperV.png, cdk3-hyperv-terminal
>
>
> While starting/stopping CDKv3 server adapter, you can observe flashing window (coming from hyperV) in terminal tab. The output looks bit ugly, there is pretty much space. When starting/stoping minishift from windows command prompt, you can see such blue flashing/blinking window, too. When I tried cygwin terminal, this did not happen. I am not sure if we can do anything about it, it seems like upstream/system issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23869:
-------------------------------
Fix Version/s: 4.5.1.AM2
(was: 4.5.x)
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.5.1.AM2
>
> Attachments: failure.png, image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24293) Lot of blank lines written to terminal when starting the CDK server
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24293?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-24293 at 8/30/17 10:52 AM:
-----------------------------------------------------------------
I believe that this jira is duplicated by https://issues.jboss.org/browse/JBIDE-24188.
[~jeffmaury] I do not think so that moving back to terminal will help to solve this problem as it was reported during the time that minishift tty output was logged in Terminal View. (If this is what you meant by Eclipse terminal).
was (Author: odockal):
I believe that this jira is duplicate to https://issues.jboss.org/browse/JBIDE-24188.
[~jeffmaury] I do not think so that moving back to terminal will help to solve this problem as it was reported during the time that minishift tty output was logged in Terminal View. (If this is what you meant by Eclipse terminal).
> Lot of blank lines written to terminal when starting the CDK server
> -------------------------------------------------------------------
>
> Key: JBIDE-24293
> URL: https://issues.jboss.org/browse/JBIDE-24293
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM2
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: terminalOutputWhenStartingCDK.txt
>
>
> Windows 10
> Version: 10.4.0.AM3
> Build id: AM3-v20170406-1058-B390
> Build date: 20170406-1058
--
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 Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24763:
--------------------------------
Sprint: devex #137 September 2017
> 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
[JBoss JIRA] (JBIDE-24886) deprecate JDK5-dependent tests or enable a way to skip them on OSX (as no JDK5 is available there)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24886?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24886:
--------------------------------
Sprint: devex #137 September 2017
> deprecate JDK5-dependent tests or enable a way to skip them on OSX (as no JDK5 is available there)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24886
> URL: https://issues.jboss.org/browse/JBIDE-24886
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> In searching for */JRE_5_HOME\|jre.5\|jre5\|jdk5\|jdk.5/*, I've only found TWO files which make use of the JDK5/JRE5 constants, so this might be fairly simple.
> {code:title=as/plugins/org.jboss.ide.eclipse.as.wtp.core/src/org/jboss/ide/eclipse/as/core/util/IJBossRuntimeResourceConstants.java}
> 63: public static final String AOP_JDK5_DEPLOYER = "jboss-aop-jdk50.deployer"; //$NON-NLS-1$
> 65: public static final String JBOSS_AOP_JDK5_JAR = "jboss-aop-jdk50.jar"; //$NON-NLS-1$
> 93: public static final String JBOSS_ASPECT_LIBRARY_JDK5_0 = "jboss-aspect-library-jdk50.jar"; //$NON-NLS-1$
> {code}
> {code:title=as/tests/org.jboss.tools.as.test.core/src/org/jboss/tools/as/test/core/TestConstants.java}
> 45: public static final String JRE_5_HOME = System.getProperty("jbosstools.test.jre.5", "C:\\apps\\java\\jre5.0\\");
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months