[JBoss JIRA] (ERT-748) [GTK3] Shell dispose slowdown [EBZ#549644]
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/ERT-748?page=com.atlassian.jira.plugin.sy... ]
Jeff MAURY updated ERT-748:
---------------------------
Sprint: devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019)
> [GTK3] Shell dispose slowdown [EBZ#549644]
> ------------------------------------------
>
> Key: ERT-748
> URL: https://issues.jboss.org/browse/ERT-748
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.13_M3, SWT, bzira
>
> Created attachment 279428
> Snippet
> GTK version: 3.22.30
> SWT version: 4928
> With the fix from Bug 547227, SWTBot unit tests are sometimes able to complete on GTK3 successfully. However sometimes the build still fails with Tycho return code 137.
> Running a loop to continuously create and dispose a ControlExample in a Shell shows that the dispose gets progressively slower.
> Doing this with the SWTBot ControlExample (a modified copy) crashes the build after less than 700 iterations, with the dispose time starting around 300 ms and ending around 2,300 ms:
> https://ci.eclipse.org/swtbot/job/swtbot-gerrit/1071/console
> By comparison, the same code with GTK2 on 2018-09 target platform crashes after more than 13,000 iterations, but the dispose time is stable around 50 ms throughout:
> https://ci.eclipse.org/swtbot/job/swtbot-gerrit/1070/console
> The slowdown problem can be reproduced locally using the original ControlExample from SWT. See the included snippet.
> Profiling this snippet shows that the majority of the time is spent in GTK._gtk_widget_destroy[native] for the Shell itself.
> main 100,341 ms (100%) 100,341 ms (100%)
> +SnippetControlExampleDispose.main () 100,341 ms (100%) 100,341 ms (100%)
> +org.eclipse.swt.widgets.Shell.dispose () 64,397 ms (64.2%) 64,397 ms (64.2%)
> +org.eclipse.swt.widgets.Widget.dispose () 64,397 ms (64.2%) 64,397 ms (64.2%)
> +org.eclipse.swt.widgets.Control.release () 64,397 ms (64.2%) 64,397 ms (64.2%)
> +org.eclipse.swt.widgets.Widget.release () 64,397 ms (64.2%) 64,397 ms (64.2%)
> +org.eclipse.swt.widgets.Widget.destroyWidget () 61,443 ms (61.2%) 61,443 ms (61.2%)
> +org.eclipse.swt.internal.gtk.GTK.gtk_widget_destroy () 61,443 ms (61.2%) 61,443 ms (61.2%)
> +org.eclipse.swt.internal.gtk.GTK._gtk_widget_destroy[native] () 61,443 ms (61.2%) 61,443 ms (61.2%)
> +org.eclipse.swt.widgets.Shell.releaseChildren () 2,954 ms (2.9%) 2,954 ms (2.9%)
> +org.eclipse.swt.examples.controlexample.ControlExample.<init> () 35,103 ms (35%) 35,103 ms (35%)
> +org.eclipse.swt.widgets.Shell.<init> () 840 ms (0.8%) 840 ms (0.8%)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (JBIDE-26840) Implement initial CRC Server adapter integration tests
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26840?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26840:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019)
> Implement initial CRC Server adapter integration tests
> ------------------------------------------------------
>
> Key: JBIDE-26840
> URL: https://issues.jboss.org/browse/JBIDE-26840
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, openshift
> Affects Versions: 4.13.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.13.0.AM1
>
>
> Following JBIDE-26824 initial implementation we will provide integration tests covering basic UI tests and integration tests. This should also cover preparation of jenkins job with necessary automation (automation of downloading/configuring CRC).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11 and add some parameters to the pom.xml
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26750:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019)
> Update CDI.itests to run on java 11 and add some parameters to the pom.xml
> --------------------------------------------------------------------------
>
> Key: JBIDE-26750
> URL: https://issues.jboss.org/browse/JBIDE-26750
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> *Description of the task from [~odockal]:*
> As I said some time ago, would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11. Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method?
> Let's put it into some utility class, that's an easiest solution.
> Update:
> I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once.
> And you can run test for both server eap and wildfly driven by param in jenkins.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26787?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26787:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019)
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.jboss.org/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> 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:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26599:
----------------------------------
Sprint: (was: devex #172 Sep 2019)
> LiveReload does not work with OpenShift3 server adapter
> -------------------------------------------------------
>
> Key: JBIDE-26599
> URL: https://issues.jboss.org/browse/JBIDE-26599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, openshift
> Affects Versions: 4.11.0.Final
> Environment: oc cluster up 3.11 from Fedora repo
> Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre...
> Devstudio + installed livereload:
> Version: 12.11.0.GA
> Build id: GA-v20190321-1925-B4244
> Build date: 20190321-1925
> JDK 11.02 + F29
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Critical
> Fix For: 4.13.0.AM1
>
> Attachments: image-2019-03-27-10-30-34-801.png
>
>
> If I try to directly connect to livereload server there is an error message:
> {code:java}
> HTTP ERROR 500
> Problem accessing /. Reason:
> Server Error
> Caused by:
> java.lang.IllegalArgumentException: Invalid URI host: null (authority: null)
> at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506)
> at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438)
> at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:502)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months