[JBoss JIRA] (JBIDE-25004) test failure in org.jboss.tools.forge.ui.ext.test
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25004?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25004.
---------------------------------
Latest builds are green on Jenkins and local build is also without issues, so closing.
> test failure in org.jboss.tools.forge.ui.ext.test
> -------------------------------------------------
>
> Key: JBIDE-25004
> URL: https://issues.jboss.org/browse/JBIDE-25004
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.5.1.AM2
> Reporter: Nick Boldt
> Assignee: George Gastaldi
> Fix For: 4.5.1.AM2
>
>
> {code}
> 15:37:05 [/qa/tools/opt/x86_64/openjdk-1.8.0.131/jre/bin/java, -Dosgi.noShutdown=false, -Dosgi.os=linux, -Dosgi.ws=gtk, -Dosgi.arch=x86_64, -javaagent:/mnt/hudson_workspace/workspace/jbosstools-forge_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-forge_master/sources/target/jacoco.exec,append=true,includes=org.jboss.tools.forge.ui*, -Xms512m, -Xmx1024m, -XX:MetaspaceSize=256m, -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-forge_master/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.4.0.v20161219-1356/org.eclipse.equinox.launcher-1.4.0.v20161219-1356.jar, -data, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/tests/org.jboss.tools.forge.ui.ext.test/target/work/data, -install, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/tests/org.jboss.tools.forge.ui.ext.test/target/work, -configuration, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/tests/org.jboss.tools.forge.ui.ext.test/target/work/configuration, -application, org.eclipse.tycho.surefire.osgibooter.uitest, -testproperties, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/tests/org.jboss.tools.forge.ui.ext.test/target/surefire.properties]
> 15:37:07 gogo: InvocationTargetException: null
> 15:37:07 java.lang.reflect.InvocationTargetException
> 15:37:07 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 15:37:07 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 15:37:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 15:37:07 at java.lang.reflect.Method.invoke(Method.java:498)
> 15:37:07 at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> 15:37:07 at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> 15:37:07 at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> 15:37:07 at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> 15:37:07 at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> 15:37:07 at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> 15:37:07 at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> 15:37:07 at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> 15:37:07 at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> 15:37:07 at java.lang.Thread.run(Thread.java:748)
> 15:37:07 Caused by: java.lang.ExceptionInInitializerError
> 15:37:07 at java.lang.System.getenv(System.java:897)
> 15:37:07 at org.apache.felix.gogo.options.Options.<init>(Options.java:309)
> 15:37:07 at org.apache.felix.gogo.options.Options.compile(Options.java:118)
> 15:37:07 at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:71)
> 15:37:07 ... 14 more
> 15:37:07 Caused by: java.lang.ArrayIndexOutOfBoundsException: 187
> 15:37:07 at java.lang.ProcessEnvironment.environ(Native Method)
> 15:37:07 at java.lang.ProcessEnvironment.<clinit>(ProcessEnvironment.java:70)
> 15:37:07 ... 18 more{code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25046:
------------------------------------------
I dont have any automatic update of the connection when I start the cdk server adapter. I created both connections without registry url. When I then start the cdk server adapter both are untouched and still dont have any registry url.
> Can't find CDK for registry discovery when 2 connections are defined for CDK
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25046
> URL: https://issues.jboss.org/browse/JBIDE-25046
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3
> Fix For: 4.5.x
>
>
> EXEC: define an Openshift connection for CDK/admin
> EXEC: define an Openshift connection for CDK/developer
> EXEC: define a CDK3 server
> EXEC: start the CDK 3 server
> ASSERT: the CDK/admin OS3 connection is updated (registry not empty)
> ASSERT: the CDK/developer OS3 connection is not updated (registry empty)
> EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon
> ASSERT: the registry URL is updated, not the error dialog is displayed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25046 at 9/18/17 6:27 AM:
-------------------------------------------------------------------
[~jeffmaury] I dont have any automatic update of the connection when I start the cdk server adapter. I created both connections without registry url. When I then start the cdk server adapter both are untouched and still dont have any registry url.
was (Author: adietish):
I dont have any automatic update of the connection when I start the cdk server adapter. I created both connections without registry url. When I then start the cdk server adapter both are untouched and still dont have any registry url.
> Can't find CDK for registry discovery when 2 connections are defined for CDK
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25046
> URL: https://issues.jboss.org/browse/JBIDE-25046
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3
> Fix For: 4.5.x
>
>
> EXEC: define an Openshift connection for CDK/admin
> EXEC: define an Openshift connection for CDK/developer
> EXEC: define a CDK3 server
> EXEC: start the CDK 3 server
> ASSERT: the CDK/admin OS3 connection is updated (registry not empty)
> ASSERT: the CDK/developer OS3 connection is not updated (registry empty)
> EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon
> ASSERT: the registry URL is updated, not the error dialog is displayed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months