[JBoss JIRA] (JBIDE-19884) cdi.ui test failure
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19884?page=com.atlassian.jira.plugi... ]
Rastislav Wagner reassigned JBIDE-19884:
----------------------------------------
Assignee: Rastislav Wagner (was: Alexey Kazakov)
> cdi.ui test failure
> -------------------
>
> Key: JBIDE-19884
> URL: https://issues.jboss.org/browse/JBIDE-19884
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Beta1
> Reporter: Alexey Kazakov
> Assignee: Rastislav Wagner
> Fix For: 4.3.0.Beta1
>
>
> {code}
> testCDINamedBeanDialogSearch(org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest) Time elapsed: 6.177 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Unexpected editor is opened for CDI Named Bean 'blackWidow': SpiderProducer.java
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.find(OpenCDINamedBeanDialogTest.java:74)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.testCDINamedBeanDialogSearch(OpenCDINamedBeanDialogTest.java:32)
> testCDINamedBeanDialogSearchShortHand(org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest) Time elapsed: 5.786 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Unexpected editor is opened for CDI Named Bean 'blackWidow': SpiderProducer.java
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.find(OpenCDINamedBeanDialogTest.java:74)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.testCDINamedBeanDialogSearchShortHand(OpenCDINamedBeanDialogTest.java:38)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months
[JBoss JIRA] (JBIDE-19884) cdi.ui test failure
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19884?page=com.atlassian.jira.plugi... ]
Rastislav Wagner reassigned JBIDE-19884:
----------------------------------------
Assignee: Alexey Kazakov (was: Rastislav Wagner)
> cdi.ui test failure
> -------------------
>
> Key: JBIDE-19884
> URL: https://issues.jboss.org/browse/JBIDE-19884
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Beta1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
>
> {code}
> testCDINamedBeanDialogSearch(org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest) Time elapsed: 6.177 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Unexpected editor is opened for CDI Named Bean 'blackWidow': SpiderProducer.java
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.find(OpenCDINamedBeanDialogTest.java:74)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.testCDINamedBeanDialogSearch(OpenCDINamedBeanDialogTest.java:32)
> testCDINamedBeanDialogSearchShortHand(org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest) Time elapsed: 5.786 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Unexpected editor is opened for CDI Named Bean 'blackWidow': SpiderProducer.java
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.find(OpenCDINamedBeanDialogTest.java:74)
> at org.jboss.tools.cdi.ui.test.wizard.OpenCDINamedBeanDialogTest.testCDINamedBeanDialogSearchShortHand(OpenCDINamedBeanDialogTest.java:38)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months
[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19786:
------------------------------------------
I built and deployed the latest openshift-restclient-java library and embedded into org.jboss.tools.openshift.client.
With the changes in JBIDE-19829 I unfortunately still cant log in, I get stuck in a blank screen:
# EXEC: launch connection wizard
# EXEC: provide https://console.stg.openshift.com as Server url
# EXEC: hit "retrieve" in the authentication pane
# ASSERT: dialog pops up with RH single sign on
!retrieve-dialog-1.png!
# EXEC: provide your kerberos-username and pin+vpn-key
Result:
The dialog gets blank
!retrieve-dialog-2.png!
> Connection wizard: cannot connect to console.stg.openshift.com
> --------------------------------------------------------------
>
> Key: JBIDE-19786
> URL: https://issues.jboss.org/browse/JBIDE-19786
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: retrieve-dialog-1.png, retrieve-dialog-2.png, unable-to-connect.png, webconsole.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months
[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19786 at 6/2/15 7:52 AM:
------------------------------------------------------------------
I built and deployed the latest openshift-restclient-java library and embedded into org.jboss.tools.openshift.client.
With the changes in JBIDE-19829 I unfortunately still cant log in, I get stuck in a blank screen:
# EXEC: launch connection wizard
# EXEC: provide https://console.stg.openshift.com as Server url
# EXEC: hit "retrieve" in the authentication pane
# ASSERT: dialog pops up with RH single sign on
!retrieve-dialog-1.png!
# EXEC: provide your kerberos-username and pin+vpn-key
Result:
The dialog gets blank
!retrieve-dialog-2.png!
was (Author: adietish):
I built and deployed the latest openshift-restclient-java library and embedded into org.jboss.tools.openshift.client.
With the changes in JBIDE-19829 I unfortunately still cant log in, I get stuck in a blank screen:
# EXEC: launch connection wizard
# EXEC: provide https://console.stg.openshift.com as Server url
# EXEC: hit "retrieve" in the authentication pane
# ASSERT: dialog pops up with RH single sign on
!retrieve-dialog-1.png!
# EXEC: provide your kerberos-username and pin+vpn-key
Result:
The dialog gets blank
!retrieve-dialog-2.png!
> Connection wizard: cannot connect to console.stg.openshift.com
> --------------------------------------------------------------
>
> Key: JBIDE-19786
> URL: https://issues.jboss.org/browse/JBIDE-19786
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: retrieve-dialog-1.png, retrieve-dialog-2.png, unable-to-connect.png, webconsole.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months
[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19853:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
> GTK3 (only): Erroneous labels in application wizard tree
> --------------------------------------------------------
>
> Key: JBIDE-19853
> URL: https://issues.jboss.org/browse/JBIDE-19853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png
>
>
> When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded.
> When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way:
> !gtk2-new-app-wizard-1.png!
> unfolding the "Basic Cartridges" produces the following:
> !gtk2-new-app-wizard-2.png!
> Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows:
> !gtk3-new-app-wizard-1.png!
> ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same:
> !gtk3-new-app-wizard-2.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months
[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-18672:
--------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> cannot run ionic tabs (the default) app with cordovasim
> -------------------------------------------------------
>
> Key: JBIDE-18672
> URL: https://issues.jboss.org/browse/JBIDE-18672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: Mac OS X, JavaFX
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: upstream
> Fix For: 4.3.0.Beta2
>
>
> run:
> ionic start ionic-demo
> import ionic-demo
> run as > cordova sim
> try use the app, click back.
> Two issues:
> 1) cordova sim complains about app.appexit not being supported
> 2) when trying to click do not show again I get the following in the cordovasim error log:
> Outstanding resource locks detected:
> ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total
> 84 total resources being managed
> average resource age is 15.1 frames
> 0 resources at maximum supported age (0.0%)
> 16 resources marked permanent (19.0%)
> 17 resources have had mismatched locks (20.2%)
> 17 resources locked (20.2%)
> 30 resources contain interesting data (35.7%)
> 0 resources disappeared (0.0%)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months