[JBoss JIRA] (JBIDE-23764) Scaling To: wrong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23764:
-------------------------------------
Story Points: 8 (was: 1)
> Scaling To: wrong number of current replicas shown at times
> -----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scale-to-dialog.png
>
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wrong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23764:
------------------------------------------
merged into master.
> Scaling To: wrong number of current replicas shown at times
> -----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scale-to-dialog.png
>
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4258) Could not resolve modules m2e and testng
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4258:
----------------------------------
Summary: Could not resolve modules m2e and testng
Key: JBDS-4258
URL: https://issues.jboss.org/browse/JBDS-4258
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: build, rpm
Affects Versions: 10.3.0.AM2
Environment: RHEL7, HRSCL 2.4. Alpha 1.0
Reporter: Lukáš Valach
Assignee: Nick Boldt
Attachments: rh-eclipse46-devstudio10.3.log.with_RHSCL_2.4.alfa_1.0.20170126-0712.txt
Devstudio installed upon rh-eclipse46-base from HRSCL 2.4. Alpha 1.0 (1) fails to start because of bundle conflict.
Base from HRSCL 2.4. newly contains m2e and testng which are also contained in Devstudio. So we probably need to remove m2e and testng from Devstudio.
(1) http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-Alpha...
Log: [^rh-eclipse46-devstudio10.3.log.with_RHSCL_2.4.alfa_1.0.20170126-0712.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23761:
------------------------------------
This appears to be fixed again. And has stayed that way for 2 days.
http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas... contains the 3.2.3.v2017 version of as.reddeer plugin.
If you're happy and you know it, click "Resolve."
> ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23761
> URL: https://issues.jboss.org/browse/JBIDE-23761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
>
> [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute?
> [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas...
> [7:31 AM] Pavol Srna: what do you think?
> [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild?
> [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2].
> [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
> [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> Submit PR against this:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1028) SY - Update tests with new components added by Integration Pack
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1028:
----------------------------------------
Summary: SY - Update tests with new components added by Integration Pack
Key: JBTIS-1028
URL: https://issues.jboss.org/browse/JBTIS-1028
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: QE, switchyard
Affects Versions: 4.4.0.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.4.0.Final
Two new components were introduced due to changes in Integration Pack
- BPM (jBPM) Integration Pack
- Rules (Drools) Integration Pack
which cannot be used with the original ones.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1024) SY - Fix SwitchYardEditorImplementationsTest
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1024?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBTIS-1024.
------------------------------------
Resolution: Rejected
Not a bug. We have to disable SWT_GTK3 as follows
{code}
export SWT_GTK3=0
{code}
(In my case I disabled SWT-GTK3 which is wrong name)
> SY - Fix SwitchYardEditorImplementationsTest
> --------------------------------------------
>
> Key: JBTIS-1024
> URL: https://issues.jboss.org/browse/JBTIS-1024
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: QE, switchyard
> Affects Versions: 4.4.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.4.0.Final
>
> Attachments: org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest.png
>
>
> Error Message
> No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.custom.CCombo]
> class org.eclipse.swt.custom.CCombo with text 'EXECUTE'
> Stacktrace
> org.jboss.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.custom.CCombo]
> class org.eclipse.swt.custom.CCombo with text 'EXECUTE'
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:47)
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:103)
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:78)
> at org.jboss.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:41)
> at org.jboss.tools.switchyard.reddeer.widget.DefaultCCombo.<init>(DefaultCCombo.java:32)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addItem(ImplementationKnowledgePage.java:135)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addOperation(ImplementationKnowledgePage.java:49)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkOperationsProperties(SwitchYardEditorImplementationsTest.java:732)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkDroolsOperationsProperties(SwitchYardEditorImplementationsTest.java:722)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest(SwitchYardEditorImplementationsTest.java:455)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months