[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3903:
---------------------------------
Hi folks,
What do we want to document for users about this issue? Is it just that they need to install Docker separately from the devsuite installation (or beforehand) to ensure the docker connection is created? Or that they should start the CDK server to create the docker connection (after docker is already installed and set up separately)?
> Platform Installer does not Setup Docker Env-Vars
> -------------------------------------------------
>
> Key: JBDS-3903
> URL: https://issues.jboss.org/browse/JBDS-3903
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 10.0.0.Alpha1
> Environment: Windows
> Reporter: Thomas Mäder
> Assignee: Xavier Coulon
>
> I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection.
> Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection.
> As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-874) Test 'addDroolsImplementationWithNewJavaInterfaceTest' sometimes fails
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-874?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-874:
------------------------------------
Attachment: org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest.png
> Test 'addDroolsImplementationWithNewJavaInterfaceTest' sometimes fails
> ----------------------------------------------------------------------
>
> Key: JBTIS-874
> URL: https://issues.jboss.org/browse/JBTIS-874
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: QE, switchyard
> Affects Versions: 4.3.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Attachments: org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest.png
>
>
> Error Message
> Timeout after: 60 s.: an item matching Matcher matching text to regular expression '.*AgendaStats.*' in
> SwitchYardServiceChannel - org.switchyard.component.common.knowledge.service
> Stacktrace
> {code}
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: an item matching Matcher matching text to regular expression '.*AgendaStats.*' in
> SwitchYardServiceChannel - org.switchyard.component.common.knowledge.service
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addClass(ImplementationKnowledgePage.java:165)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addItem(ImplementationKnowledgePage.java:144)
> at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addListener(ImplementationKnowledgePage.java:99)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkAdvancedProperties(SwitchYardEditorImplementationsTest.java:792)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkDroolsAdvancedProperties(SwitchYardEditorImplementationsTest.java:782)
> at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest(SwitchYardEditorImplementationsTest.java:471)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-874) Test 'addDroolsImplementationWithNewJavaInterfaceTest' sometimes fails
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-874:
---------------------------------------
Summary: Test 'addDroolsImplementationWithNewJavaInterfaceTest' sometimes fails
Key: JBTIS-874
URL: https://issues.jboss.org/browse/JBTIS-874
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, switchyard
Affects Versions: 4.3.1.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Error Message
Timeout after: 60 s.: an item matching Matcher matching text to regular expression '.*AgendaStats.*' in
SwitchYardServiceChannel - org.switchyard.component.common.knowledge.service
Stacktrace
{code}
org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: an item matching Matcher matching text to regular expression '.*AgendaStats.*' in
SwitchYardServiceChannel - org.switchyard.component.common.knowledge.service
at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37)
at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addClass(ImplementationKnowledgePage.java:165)
at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addItem(ImplementationKnowledgePage.java:144)
at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addListener(ImplementationKnowledgePage.java:99)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkAdvancedProperties(SwitchYardEditorImplementationsTest.java:792)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkDroolsAdvancedProperties(SwitchYardEditorImplementationsTest.java:782)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest(SwitchYardEditorImplementationsTest.java:471)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-850) Improve stability of adding a new connection
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-850?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-850.
-----------------------------------
Fix Version/s: 4.3.2.CR1
Resolution: Done
pushed to master
> Improve stability of adding a new connection
> --------------------------------------------
>
> Key: JBTIS-850
> URL: https://issues.jboss.org/browse/JBTIS-850
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: BPMN2, QE
> Affects Versions: 4.3.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Jozef Marko
> Fix For: 4.3.2.CR1
>
>
> It seems that the logic for adding a new connection between two components doesn't always work. Please see the error which occured on jawa34g1
> {code}
> org.jboss.tools.bpmn2.ui.bot.complex.test.testcase.ComplexParalellSplitJoinTest.jbpm6ComplexTest default (from org.jboss.tools.bpmn2.ui.bot.test.SmokeTests)
> Failing for the past 4 builds (Since Unstable#320 )
> Took 30 sec.
> add description
> Error Message
> Timeout after: 10 s.: the number of edit parts is 37
> Stacktrace
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: the number of edit parts is 37
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25)
> at org.jboss.tools.bpmn2.reddeer.GEFProcessEditor.addConnectionFromPalette(GEFProcessEditor.java:136)
> at org.jboss.tools.bpmn2.reddeer.editor.Element$ConnectionAdded.test(Element.java:567)
> at org.jboss.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:80)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:122)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25)
> at org.jboss.tools.bpmn2.reddeer.editor.Element.connectTo(Element.java:298)
> at org.jboss.tools.bpmn2.reddeer.editor.Element.connectTo(Element.java:287)
> at org.jboss.tools.bpmn2.ui.bot.complex.test.testcase.ComplexParalellSplitJoinTest.model(ComplexParalellSplitJoinTest.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23089) when central tests crash job breaks due to dirty workspace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23089?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23089:
------------------------------------
Applied in master but not 4.4.1.x so moving fixversion to 4.4.2.AM1
> when central tests crash job breaks due to dirty workspace
> ----------------------------------------------------------
>
> Key: JBIDE-23089
> URL: https://issues.jboss.org/browse/JBIDE-23089
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central
> Affects Versions: 4.4.1.Final, 4.4.2.AM1
> Reporter: Nick Boldt
> Fix For: 4.4.2.AM1
>
>
> {code}
> 15:00:03 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.26.0:build-qualifier (default-build-qualifier) on project org.jboss.tools.central.test: Working tree is dirty.
> 15:00:03 [ERROR] git status central/tests/org.jboss.tools.central.test:
> 15:00:03 [ERROR]
> 15:00:03 [ERROR] Untracked files:
> 15:00:03 [ERROR] central/tests/org.jboss.tools.central.test/hs_err_pid29878.log
> 15:00:03 [ERROR]
> 15:00:03 [ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above).
> 15:00:03 [ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring
> 15:00:03 [ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin{code}
> -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Workaround:
> wipe workspace, try again
> Solution:
> add hs_err_pid*.log to .gitignore
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months