April 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4713) Fix installer tests

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4713?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4713: ------------------------------------- Resolving in favor of JBDS-4770. > Fix installer tests > ------------------- > > Key: JBDS-4713 > URL: https://issues.jboss.org/browse/JBDS-4713 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.0.0.GA > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.12.0.AM1 > > > Fix devstudio installer tests on jenkins, suites: > * [BYOE Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Post Installation Tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Devstudio Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4713) Fix installer tests

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4713?page=com.atlassian.jira.plugin.... ] Ondrej Dockal resolved JBDS-4713. --------------------------------- Resolution: Done > Fix installer tests > ------------------- > > Key: JBDS-4713 > URL: https://issues.jboss.org/browse/JBDS-4713 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.0.0.GA > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.12.0.AM1 > > > Fix devstudio installer tests on jenkins, suites: > * [BYOE Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Post Installation Tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Devstudio Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4756: ------------------------------------- But since this issue occurs only on cental CI mac machines, locally everything works as expected, I am resolving this issue. Verification will shows whether problem resides in network jdk or cci machines. > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Environment: CentralCI > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.12.0.AM1 > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal resolved JBDS-4756. --------------------------------- Resolution: Done > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Environment: CentralCI > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.12.0.AM1 > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26567) Remove old tests from integration tests repo

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26567?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26567: ---------------------------------- Sprint: devex #165 April 2019 (was: devex #164 April 2019) > Remove old tests from integration tests repo > -------------------------------------------- > > Key: JBIDE-26567 > URL: https://issues.jboss.org/browse/JBIDE-26567 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian, integration-tests > Affects Versions: 4.11.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.0.AM1 > > > From meeting doc: > [jkopriva] - remove not supported itests and plugins from integration tests repo? > arquilian - OK -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26575) OpenShift ITests: ITests are failing due to dialog popups

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26575?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26575: ---------------------------------- Sprint: devex #165 April 2019 (was: devex #164 April 2019) > OpenShift ITests: ITests are failing due to dialog popups > --------------------------------------------------------- > > Key: JBIDE-26575 > URL: https://issues.jboss.org/browse/JBIDE-26575 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26579) Add Sonar in integration tests repo

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26579?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26579: ---------------------------------- Sprint: devex #165 April 2019 (was: devex #164 April 2019) > Add Sonar in integration tests repo > ----------------------------------- > > Key: JBIDE-26579 > URL: https://issues.jboss.org/browse/JBIDE-26579 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.11.0.Final > Environment: Jenkins > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26574) Server ITests: Update eap7x-compatibility profile in ITests for WildFly

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26574?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26574: ---------------------------------- Sprint: devex #165 April 2019 (was: devex #164 April 2019) > Server ITests: Update eap7x-compatibility profile in ITests for WildFly > ----------------------------------------------------------------------- > > Key: JBIDE-26574 > URL: https://issues.jboss.org/browse/JBIDE-26574 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.11.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.0.AM1 > > > EAP wants to also tests WildFly with profile eap7x-compatibility. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26278: ---------------------------------- Sprint: devex #154 September 2018, devex #155 September 2018, devex #165 April 2019 (was: devex #154 September 2018, devex #155 September 2018, devex #164 April 2019) > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.12.0.AM1 > > Attachments: log.txt > > > TBD -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25814: ---------------------------------- Sprint: devex #165 April 2019 (was: devex #164 April 2019) > Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25814 > URL: https://issues.jboss.org/browse/JBIDE-25814 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: André Dietisheim > Assignee: Josef Kopriva > Priority: Major > Labels: server_adapter_wizard > Fix For: 4.12.0.AM1 > > > steps: > # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online) > # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application > # ASSERT: Connection selection page pops up > # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further. > # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter > # ASSERT: Connection selection page pops up > Result: > the connection selection page has the 1st connection selected, not the one that we used most recently. > (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently) > Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 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 April 2019