[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:
-------------------------------
Fix Version/s: 4.13.0.Final
(was: 4.13.0.AM1)
> 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.Final
>
>
> 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)
4 years, 12 months
[JBoss JIRA] (ERT-759) ToolItem setDisabledImage isn't used [EBZ#302918]
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/ERT-759?page=com.atlassian.jira.plugin.sy... ]
Jeff MAURY updated ERT-759:
---------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019)
> ToolItem setDisabledImage isn't used [EBZ#302918]
> -------------------------------------------------
>
> Key: ERT-759
> URL: https://issues.jboss.org/browse/ERT-759
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> I recently had a disabled handler for a command that also provided icon in the commandImages extension point. However, the disabled icon was not honored by the toolbar item, and instead Eclipse drew its own clumsy icon derived from the normal one. Setting the disabled icon directly on the toolbar contribution worked.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (JBIDE-26807) Add missing templates of the OSes used in CodeReady Studio certification matrix into PSI jenkins
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26807?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26807:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019 (was: devex #172 Sep 2019)
> Add missing templates of the OSes used in CodeReady Studio certification matrix into PSI jenkins
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26807
> URL: https://issues.jboss.org/browse/JBIDE-26807
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.13.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: jenkins
> Fix For: 4.13.0.Final
>
>
> Add missing jenkins cloud templates into new PSI jenkins with proper flavors and label (medium, x64, jbds, etc). OSes missing:
> * fedora 29, 30
> * static macs: bigmek, domek, zamek, dev-platform-mac1, dev-platform-mac2
> * ubuntu 19.04, 18.04
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (JBIDE-23666) Update or remove quickstarts on Central Home Page
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23666:
-------------------------------
Sprint: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019, devex #173 Oct 2019 (was: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019)
> Update or remove quickstarts on Central Home Page
> -------------------------------------------------
>
> Key: JBIDE-23666
> URL: https://issues.jboss.org/browse/JBIDE-23666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.3.AM1
> Environment: Red Hat JBoss Developer Studio
> Version: 10.3.0.AM1
> Build id: AM1-v20161225-1238-B6761
> Build date: 20161225-1238
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.Final
>
> Attachments: central-wizards.png
>
>
> Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur:
> {code:java}
> Description Resource Path Location Type
> Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem
> Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem
> No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem
> No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem
> No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem
> {code}
> For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24899:
-------------------------------
Sprint: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019, devex #173 Oct 2019 (was: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019)
> Deploy Docker Image wizard: Image not found
> -------------------------------------------
>
> Key: JBIDE-24899
> URL: https://issues.jboss.org/browse/JBIDE-24899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.Final
>
> Attachments: image-2017-08-29-09-50-20-927.png
>
>
> Exception in Error log:
> {code:java}
> Failed to inspect image: '172.30.1.1:5000/test/hola:latest'
> com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023)
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326)
> ... 5 more
> Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found
> at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008)
> at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816)
> at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92)
> at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773)
> at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198)
> at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340)
> at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> eclipse.buildId=11.1.0.AM1-v20170824-1835-B873
> java.version=1.8.0_141
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4735:
-----------------------------
Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019, devex #166 May 2019, devex #167 June 2019, devex #168 June 2019, devex #169 July 2019, devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019, devex #173 Oct 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019, devex #166 May 2019, devex #167 June 2019, devex #168 June 2019, devex #169 July 2019, devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.9.0.GA
> Environment: manually Fedora 28, automation
> Reporter: Vojtech Prusa
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.13.0.AM1
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png
>
>
> There is "openInIDE" used in 3 places in "main.min.js" in central source code*. When the central reloads and works normally, "openInIDE" is a function (probably defined in Java code or somewhere out of the "main.min.js" file) with following implementation:
> function openInIDE() {
> var result = callJava(1, '9aee3b4a3f3b40ed26f47d66375b25e3', Array.prototype.slice.call(arguments));
> if (typeof result == 'string' && result.indexOf('org.eclipse.swt.browser.error') == 0) {
> var error = new Error(result.substring(29));
> throw error;
> }
> return result;
> }
> After the issue appears, "typedef openInIDE" is undefined, which causes probably the issues.
> *Additional information to the 3 places, where "openInIDE" appears - it appears in 2 functions:
> - registerButtonClicks() - here is the "openInIDE" needed for loading and displaying the central correctly
> - delegateToIDE(a, b) - here is the "openInIDE" needed for opening the wizard to the quickstart
> OLDER DESCRIPTION (does not describes the issue enough, but I decided to keep it for more details about the issue):
> ----------------------------------------------------------------------------------------------------------------------
> Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
> Nothing in Error log view.
> Restarting devstudio solves the issue.
> Adding screen and central tar of:
> devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
> Addition info:
> Considering that central itests fails for this sometimes fresh installation without restart may cause this. Although it happen again after running devstudio for some time and restarting Central view.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 12 months
[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)
4 years, 12 months