October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-805) Fuse: Fix all automated tests for 8.0.0

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-805?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-805: ------------------------------- Affects Version/s: 4.3.2.CR1 > Fuse: Fix all automated tests for 8.0.0 > --------------------------------------- > > Key: JBTIS-805 > URL: https://issues.jboss.org/browse/JBTIS-805 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final, 4.3.2.CR1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.3.2.CR1 > > > automated tests have to be adapted to changes in Fuse Tooling 8.0.0.Beta3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-805) Fuse: Fix all automated tests for 8.0.0

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-805?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-805: ------------------------------- Fix Version/s: 4.3.2.CR1 > Fuse: Fix all automated tests for 8.0.0 > --------------------------------------- > > Key: JBTIS-805 > URL: https://issues.jboss.org/browse/JBTIS-805 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final, 4.3.2.CR1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.3.2.CR1 > > > automated tests have to be adapted to changes in Fuse Tooling 8.0.0.Beta3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-805) Fuse: Fix all automated tests for 8.0.0

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-805?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-805: ------------------------------- Summary: Fuse: Fix all automated tests for 8.0.0 (was: Fuse: Fix all automated tests for 8.0.0.Beta3) > Fuse: Fix all automated tests for 8.0.0 > --------------------------------------- > > Key: JBTIS-805 > URL: https://issues.jboss.org/browse/JBTIS-805 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > > automated tests have to be adapted to changes in Fuse Tooling 8.0.0.Beta3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22965: --------------------------------------- [~dbocharov], you're correct that Step 1 is done and the eng-ops ticket for nested VM is stuck. So the workaround is to start running the test on a windows machine connected to central ci. One machine is now set up and I will try to set up a nightly job soon(tm) (hopefully today). > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4086) Console is badly rendering some characters when starting Container Development Environment

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4086?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4086: ---------------------------------- Component/s: server > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBDS-4086 > URL: https://issues.jboss.org/browse/JBDS-4086 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Priority: Minor > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4086) Console is badly rendering some characters when starting Container Development Environment

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4086?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4086: ---------------------------------- Attachment: screenshot-1.png > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBDS-4086 > URL: https://issues.jboss.org/browse/JBDS-4086 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Priority: Minor > Attachments: screenshot-1.png > > > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4086) Console is badly rendering some characters when starting Container Development Environment

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4086?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4086: ---------------------------------- Description: - there is a special character before the [KProgress - what means K for KProgress? {noformat} Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cdkv2'... [KProgress: 10% [KProgress: 20% [KProgress: 90% [K==> default: Matching MAC address for NAT networking... {noformat} was: {noformat} Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cdkv2'... [KProgress: 10% [KProgress: 20% [KProgress: 90% [K==> default: Matching MAC address for NAT networking... {noformat} > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBDS-4086 > URL: https://issues.jboss.org/browse/JBDS-4086 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Priority: Minor > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ] Václav Kadlčík updated JBDS-4085: --------------------------------- Summary: unresolved bundles, slow initial start up (was: unresolved bundles, slow start up) > unresolved bundles, slow initial start up > ----------------------------------------- > > Key: JBDS-4085 > URL: https://issues.jboss.org/browse/JBDS-4085 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Reporter: Václav Kadlčík > Attachments: unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log > > > Tested: > * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm > * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...) > rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken). > I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios: > * "min" in the name means minimal install rh-eclipse46-devstudio > * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio" > * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio > As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example: > initial start of rh-eclipse46: 40s > same as above with rh-eclipse46-devstudio: 120s > initial start of rh-eclipse46* except devstudio: 50s > same as above with rh-eclipse46-devstudio: 140s > Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4086) Console is badly rendering some characters when starting Container Development Environment

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4086: ------------------------------------- Summary: Console is badly rendering some characters when starting Container Development Environment Key: JBDS-4086 URL: https://issues.jboss.org/browse/JBDS-4086 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: cdk Affects Versions: 10.1.0.GA Reporter: Aurélien Pupier Priority: Minor {noformat} Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'cdkv2'... [KProgress: 10% [KProgress: 20% [KProgress: 90% [K==> default: Matching MAC address for NAT networking... {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4085) unresolved bundles, slow start up

by Václav Kadlčík (JIRA)

Václav Kadlčík created JBDS-4085: ------------------------------------ Summary: unresolved bundles, slow start up Key: JBDS-4085 URL: https://issues.jboss.org/browse/JBDS-4085 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: rpm Reporter: Václav Kadlčík Attachments: unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log Tested: * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...) rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken). I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios: * "min" in the name means minimal install rh-eclipse46-devstudio * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio" * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example: initial start of rh-eclipse46: 40s same as above with rh-eclipse46-devstudio: 120s initial start of rh-eclipse46* except devstudio: 50s same as above with rh-eclipse46-devstudio: 140s Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016