August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24878) Sometimes devstudio got stuck on Central CI rhel slave

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24878?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24878: ---------------------------------- Story Points: 5 > Sometimes devstudio got stuck on Central CI rhel slave > ------------------------------------------------------ > > Key: JBIDE-24878 > URL: https://issues.jboss.org/browse/JBIDE-24878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.1.AM1 > Environment: rhel > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: central-ci, jenkins > Fix For: 4.5.1.AM2 > > Attachments: error.log > > > Sometimes it happens that devstudio got stuck while run on rhel slave in our central CI. > Error log suggests this: > {code} > !ENTRY org.eclipse.osgi 4 0 2017-08-18 11:06:50.627 > !MESSAGE Application error > !STACK 1 > org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] > at org.eclipse.swt.SWT.error(SWT.java:4559) > at org.eclipse.swt.widgets.Display.createDisplay(Display.java:948) > at org.eclipse.swt.widgets.Display.create(Display.java:935) > at org.eclipse.swt.graphics.Device.<init>(Device.java:174) > at org.eclipse.swt.widgets.Display.<init>(Display.java:559) > at org.eclipse.swt.widgets.Display.<init>(Display.java:550) > at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:781) > at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:160) > at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:181) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24592) Study Foreman documentation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24592?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24592: ---------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.1.AM2 > > > This issue consists of going through foreman documentation, tutorials and manuals. > Afterwards, it could be possible to address another steps in this process. > Docs: > https://www.theforeman.org/manuals/1.15/index.html > https://beryju.org/en/blog/getting-started-foreman-part-1#install_os > http://projects.theforeman.org/issues/432 > https://groups.google.com/forum/#!topic/foreman-users/FP9uTb8TAFY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24656) Split CDK3 server adapter integration tests into separated classes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24656?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24656: ---------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Split CDK3 server adapter integration tests into separated classes > ------------------------------------------------------------------ > > Key: JBIDE-24656 > URL: https://issues.jboss.org/browse/JBIDE-24656 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.5.1.AM2 > > > I decided to divide quite time-consuming CDK server adapter integration tests into smaller test cases due to time that is needed to run all of these test cases in one test class. The one class with all server adapter test cases will be divide into 4 independent classes. > org.jboss.tools.cdk.ui.bot.test.server.adapter.CDK3IntegrationTest will be split into > CDK3IntegrationStartTest > CDK3IntegrationRestartTest > CDK3IntegrationDockerTest > CDK3IntegrationOpenshiftTest > It will be possible to run cdk pr-check job much faster, if it would contain only one complex test case, instead of 4 test cases that each requires to start cdk 3 server adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24760) Add windows as supported platform for cdk-scripts

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24760?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24760: ---------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Add windows as supported platform for cdk-scripts > ------------------------------------------------- > > Key: JBIDE-24760 > URL: https://issues.jboss.org/browse/JBIDE-24760 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.5.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci, jenkins > Fix For: 4.5.1.AM2 > > > See https://github.com/odockal/cdk-scripts/issues/4. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24838) Test if CDK3 can run on win images in openstack 10, virtualbox and hyperv hypervisors

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24838?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24838: ---------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Test if CDK3 can run on win images in openstack 10, virtualbox and hyperv hypervisors > ------------------------------------------------------------------------------------- > > Key: JBIDE-24838 > URL: https://issues.jboss.org/browse/JBIDE-24838 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.5.1.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk, central-ci > Fix For: 4.5.1.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24661) Incorporates console output into cdk3 integration tests

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24661?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24661: ---------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Incorporates console output into cdk3 integration tests > ------------------------------------------------------- > > Key: JBIDE-24661 > URL: https://issues.jboss.org/browse/JBIDE-24661 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk > Fix For: 4.5.1.AM2 > > > After https://issues.jboss.org/browse/JBIDE-24587 is merged, existing cdk intergration tests should incorporates new feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24873: ---------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) Sprint: devex #137 September 2017 > Add management itests to eap jbds compatibility jenkins job > ----------------------------------------------------------- > > Key: JBIDE-24873 > URL: https://issues.jboss.org/browse/JBIDE-24873 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > > The EAP team would like us to add this test > org.jboss.tools.as.management.itests > to their compatibility job: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... > details here: EAP7-194 > The test to be added is run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Cc: [~rob.stryker] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-24877. --------------------------------- Verified in 11.1.0.AM2-v20170828-2243-B917. > CDK 2 detection results in CDK 3 adapter creation > ------------------------------------------------- > > Key: JBIDE-24877 > URL: https://issues.jboss.org/browse/JBIDE-24877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.1.AM2 > > > As described by [~odockal] in JBIDE-24447: > When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2. > This relative path normally translate to a structure like this: > $SOME_DIR/devstudio > $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE > BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24878) Sometimes devstudio got stuck on Central CI rhel slave

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24878?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24878 at 8/29/17 6:59 AM: ---------------------------------------------------------------- I have updated rhel-based images to be build upon rhel-7.4-server-x86_64-released. It happened that in the process of pushing some changes to rhel images the older 7.3 rhel image was used. So this might helps. was (Author: odockal): I have updated rhel-based images to be build upon rhel-7.4-server-x86_64-released. It happned that in the process of pushing some changes to rhel images the older 7.3 rhel image was used. So this might helps. > Sometimes devstudio got stuck on Central CI rhel slave > ------------------------------------------------------ > > Key: JBIDE-24878 > URL: https://issues.jboss.org/browse/JBIDE-24878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.1.AM1 > Environment: rhel > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: central-ci, jenkins > Fix For: 4.5.1.AM2 > > Attachments: error.log > > > Sometimes it happens that devstudio got stuck while run on rhel slave in our central CI. > Error log suggests this: > {code} > !ENTRY org.eclipse.osgi 4 0 2017-08-18 11:06:50.627 > !MESSAGE Application error > !STACK 1 > org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] > at org.eclipse.swt.SWT.error(SWT.java:4559) > at org.eclipse.swt.widgets.Display.createDisplay(Display.java:948) > at org.eclipse.swt.widgets.Display.create(Display.java:935) > at org.eclipse.swt.graphics.Device.<init>(Device.java:174) > at org.eclipse.swt.widgets.Display.<init>(Display.java:559) > at org.eclipse.swt.widgets.Display.<init>(Display.java:550) > at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:781) > at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:160) > at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:181) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24877 at 8/29/17 6:57 AM: ---------------------------------------------------------------- I will do my best not to tackle any of these is future! :D But hey, the fix solved the problem! Thanks Rob. Closing. was (Author: odockal): I will do my best to not to tackle any of these is future! :D But hey, the fix solved the problem! Thanks Rob. Closing. > CDK 2 detection results in CDK 3 adapter creation > ------------------------------------------------- > > Key: JBIDE-24877 > URL: https://issues.jboss.org/browse/JBIDE-24877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.1.AM2 > > > As described by [~odockal] in JBIDE-24447: > When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2. > This relative path normally translate to a structure like this: > $SOME_DIR/devstudio > $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE > BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017