[JBoss JIRA] (JBTIS-1123) Test ServerTest is failing with default karaf instance
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1123:
----------------------------------------
Summary: Test ServerTest is failing with default karaf instance
Key: JBTIS-1123
URL: https://issues.jboss.org/browse/JBTIS-1123
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: Fuse IDE, QE
Affects Versions: 4.3.3.Final
Reporter: Andrej Podhradsky
Assignee: Tomáš Sedmík
*Failed tests:*
{code}
The following shells remained open [Delete Server]
{code}
*Tests in error: *
{code}
ServerTest.testComplexServer:76 » CoreLayer No matching widget found with Matc...
No matching widget found with Matcher matching when all matchers match: [Widget matcher matching widgets with style: 32, Matcher matching widget with the same type as or type extending class org.eclipse.swt.widgets.Button]
class org.eclipse.swt.widgets.Shell with text 'Delete Server'
class org.eclipse.swt.widgets.Label with text ''
class org.eclipse.swt.widgets.Label with text 'Are you sure you want to delete ${karaf.name}-Fuse?'
class org.eclipse.swt.widgets.Composite with label 'Are you sure you want to delete ${karaf.name}-Fuse?'
class org.eclipse.swt.widgets.Composite with label 'Are you sure you want to delete ${karaf.name}-Fuse?'
class org.eclipse.swt.widgets.Composite with label 'Are you sure you want to delete ${karaf.name}-Fuse?'
class org.eclipse.swt.widgets.Button with label 'Are you sure you want to delete ${karaf.name}-Fuse?' with text 'Cancel'
class org.eclipse.swt.widgets.Button with label 'Are you sure you want to delete ${karaf.name}-Fuse?' with text 'OK'
Tests run: 3, Failures: 1, Errors: 2, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (JBIDE-24302) Circular fragment workflow for optional runtime use case
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24302?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24302.
---------------------------------
I never hit this issue myself. So I tried it with devstudio 10.4.0.GA and indeed, I was able to reproduce! Then I tried with 11.0.0.AM1 and couldn't reproduce there, so verified.
> Circular fragment workflow for optional runtime use case
> --------------------------------------------------------
>
> Key: JBIDE-24302
> URL: https://issues.jboss.org/browse/JBIDE-24302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> This is a tracking issue for this upstream bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=514888
>
> Rob's description:
> While playing with the changes dropped for Bug 513486, I found a small bug.
> When a runtime is optional, the wtp framework does not add the runtime fragment directly. It will only add the server fragment, and assume that the server fragment will introduce the runtime fragment in the workflow as it chooses.
> A workflow was discovered where the NewServerWizardFragment is still adding the runtime fragment before the server fragment. Since the server may also be adding that fragment later, it leads to circular behavior because the runtime fragment is in the list of fragments twice. The user will then press next continually but never advance.
> Sorry for this bug. It only happens under specific situations.
> Workflow:
> 1) new server wizard, choose server type with optional runtime
> 2) Go forward, change settings in server fragment, causing server fragment to designate runtime fragment as a child
> 3) go back to main page of server wizard to change host
> 4) Change host to 127.0.0.1
> 5) Press forward, forward, forward, etc. never ends.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21059:
---------------------------------------
[~rob.stryker], it's still the same. I followed the steps, started the container created from the Dockerfile. And then created the server adapter and started in debug mode. And now it's just "Starting", probably until the timeout is reached.
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months