[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4077:
----------------------------------
Maybe your devstudio's workspace is corrupt. Or there's something bad in your ~/.eclipse folder. Try this:
* delete ~/.eclipse, then
* install devstudio from the latest installer jar, pointing it at an empty, unused folder for its workspace when it launches.
* THEN try the tests again.
[1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.product_maste...
> Cannot run integration tests against Devstudio with latest target platform
> --------------------------------------------------------------------------
>
> Key: JBDS-4077
> URL: https://issues.jboss.org/browse/JBDS-4077
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 10.2.0.AM1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: .log, jbosstools-integration-tests.log.txt.zip, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png
>
>
> Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards.
> A full devstudio should open when the tests are run. Instead it looks like this:
> !tpfail.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4059:
----------------------------------
{code}
# as root
yum remove rh-eclipse46-devstudio
rm -fr /home/nboldt/.eclipse/*
yum install rh-eclipse46-devstudio
Installed:
ORBit2.x86_64 2.14.19-15.fc24 hsqldb.noarch 1:2.3.3-4.fc24
hsqldb-lib.noarch 1:2.3.3-4.fc24 libIDL.x86_64 0.8.14-11.fc24
rh-eclipse46-args4j.noarch 2.32-3.2.el7 rh-eclipse46-axis.noarch 1.4-29.4.el7
rh-eclipse46-base.x86_64 1-11.el7 rh-eclipse46-bouncycastle.noarch 1.54-1.4.el7
rh-eclipse46-bouncycastle-pkix.noarch 1.54-1.2.el7 rh-eclipse46-devstudio.x86_64 10.2-0.20161005.1507.el7
...
rh-eclipse46-wsil4j.noarch 1.0-12.1.el7 rh-java-common-PyXB.noarch 1.2.4-1.4.el7
...
rh-java-common-xpp3.noarch 1.1.3.8-11.12.el7 rh-java-common-xz-java.noarch 1.3-3.12.el7
rh-maven33-apache-commons-lang3.noarch 3.4-2.2.el7 rh-maven33-runtime.x86_64 1-17.el7
Complete!
{code}
Timeline:
* About 30 seconds to uninstall, then
* 3 mins to install from scratch again, including all deps.
* only about 1 minute to start Eclipse.
{code}
13:03:34 ./eclipse
13:04:47 Eclipse prompts for workspace location, I key in a new one under /tmp/, and it opens
{code}
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4059 at 10/5/16 12:39 PM:
------------------------------------------------------------
{code}
#as user
sudo su
# # as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:53:30 remediation done (~2 mins)
(~15 secs to review and click through to Finish, then 30-45 seconds for Eclipse to think about selection)
11:54:30 Installing Software dialog appears
11:58:34 prompted to restart eclipse (4 mins to download and install)
12:05:51 Eclipse *finally* opens, ready to use (over 7 mins!)
{code}
was (Author: nickboldt):
{code}
#as user
sudo su
# # as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:53:30 remediation done (~2 mins)
(15 secs to review and click through to Finish)
11:54:30 Installing Software dialog appears
11:58:34 prompted to restart eclipse (4 mins to download and install)
12:05:51 Eclipse *finally* opens, ready to use (over 7 mins!)
{code}
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4059 at 10/5/16 12:39 PM:
------------------------------------------------------------
{code}
#as user
sudo su
# as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:53:30 remediation done (~2 mins)
(~15 secs to review and click through to Finish, then 30-45 seconds for Eclipse to think about selection)
11:54:30 Installing Software dialog appears
11:58:34 prompted to restart eclipse (4 mins to download and install)
12:05:51 Eclipse *finally* opens, ready to use (over 7 mins!)
{code}
was (Author: nickboldt):
{code}
#as user
sudo su
# # as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:53:30 remediation done (~2 mins)
(~15 secs to review and click through to Finish, then 30-45 seconds for Eclipse to think about selection)
11:54:30 Installing Software dialog appears
11:58:34 prompted to restart eclipse (4 mins to download and install)
12:05:51 Eclipse *finally* opens, ready to use (over 7 mins!)
{code}
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4059 at 10/5/16 12:38 PM:
------------------------------------------------------------
{code}
#as user
sudo su
# # as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:53:30 remediation done (~2 mins)
(15 secs to review and click through to Finish)
11:54:30 Installing Software dialog appears
11:58:34 prompted to restart eclipse (4 mins to download and install)
12:05:51 Eclipse *finally* opens, ready to use (over 7 mins!)
{code}
was (Author: nickboldt):
{code}
#as user
sudo su
# # as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:52 remediation 6/15
11:52:45 remediation 11/15
11:53:30 remediation done
(15 secs to review and click through to Finish)
11:54:30 Installing Software dialog appears
11:55:20 83%
11:57:00 83%
11:58:34 prompted to restart eclipse
12:05:51 Eclipse *finally* opens, ready to use{code}
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23285:
------------------------------------
Note that this isn't really an issue of disk space in a jenkins slave, but rather when users run the i-tests themselves locally. If they're that hard, lengthy, or bloated (too much disk) then people may not run them very often, and we may miss problems. CI jobs only run on so many platforms (RHEL 6/7, Win 8.1/10)... we have no OSX CI jobs, afaik, so we'll never catch integration issues on OSX unless people run these by hand.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23285 at 10/5/16 12:34 PM:
--------------------------------------------------------------
I was not suggesting we remove old server adapters, only that we might want to performance tune the suite of integration tests by NOT running the old ones in order to save time and disk space.
To answer the question of how much disk is used, consider this 2.2G m2 repo cache being copied over into a tests/org.jboss.tools.*/target/ folder a dozen times.
{code}
cd ~/.m2/repository/.cache/maven-download-plugin; du -sch *.zip | sort
105M jboss-5.0.1.GA-jdk6.zip
108M jboss-seam-2.2.2.Final.zip
127M wildfly-8.2.0.Final.zip
128M jboss-5.1.0.GA-jdk6.zip
128M jboss-as-7.1.1.Final.zip
128M wildfly-9.0.1.Final.zip
132M wildfly-10.0.0.Final.zip
138M wildfly-10.0.0.CR2.zip
175M jboss-as-distribution-6.1.0.Final.zip
187M GateIn-3.5.0.Final-jbossas7.zip
192M GateIn-3.4.0.Final-jbossas5.zip
54M jboss-3.2.8.SP1.zip
60M hibernate-distribution-3.6.10.Final-dist.zip
61M hibernate-release-4.3.11.Final.zip
64M hibernate-distribution-3.5.3-Final-dist.zip
76M jboss-as-7.0.2.Final.zip
78M jboss-4.0.5.GA.zip
8.2M 10.x.zip
88M jboss-seam-2.0.2.SP1.zip
89M jboss-seam-distribution-2.3.0.Final-dist.zip
96M jboss-4.2.3.GA-jdk6.zip
2.2G total{code}
was (Author: nickboldt):
I was not suggesting we remove old server adapters, only that we might want to performance tune the suite of integration tests by NOT running the old ones in order to save time and disk space.
To answer the question of how much disk is used, consider this cache 2.2G cache being copied over into a tests/org.jboss.tools.*/target/ folder a dozen times.
{code}
cd ~/.m2/repository/.cache/maven-download-plugin; du -sch *.zip | sort
105M jboss-5.0.1.GA-jdk6.zip
108M jboss-seam-2.2.2.Final.zip
127M wildfly-8.2.0.Final.zip
128M jboss-5.1.0.GA-jdk6.zip
128M jboss-as-7.1.1.Final.zip
128M wildfly-9.0.1.Final.zip
132M wildfly-10.0.0.Final.zip
138M wildfly-10.0.0.CR2.zip
175M jboss-as-distribution-6.1.0.Final.zip
187M GateIn-3.5.0.Final-jbossas7.zip
192M GateIn-3.4.0.Final-jbossas5.zip
54M jboss-3.2.8.SP1.zip
60M hibernate-distribution-3.6.10.Final-dist.zip
61M hibernate-release-4.3.11.Final.zip
64M hibernate-distribution-3.5.3-Final-dist.zip
76M jboss-as-7.0.2.Final.zip
78M jboss-4.0.5.GA.zip
8.2M 10.x.zip
88M jboss-seam-2.0.2.SP1.zip
89M jboss-seam-distribution-2.3.0.Final-dist.zip
96M jboss-4.2.3.GA-jdk6.zip
2.2G total{code}
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23285:
------------------------------------
I was not suggesting we remove old server adapters, only that we might want to performance tune the suite of integration tests by NOT running the old ones in order to save time and disk space.
To answer the question of how much disk is used, consider this cache 2.2G cache being copied over into a tests/org.jboss.tools.*/target/ folder a dozen times.
{code}
cd ~/.m2/repository/.cache/maven-download-plugin; du -sch *.zip | sort
105M jboss-5.0.1.GA-jdk6.zip
108M jboss-seam-2.2.2.Final.zip
127M wildfly-8.2.0.Final.zip
128M jboss-5.1.0.GA-jdk6.zip
128M jboss-as-7.1.1.Final.zip
128M wildfly-9.0.1.Final.zip
132M wildfly-10.0.0.Final.zip
138M wildfly-10.0.0.CR2.zip
175M jboss-as-distribution-6.1.0.Final.zip
187M GateIn-3.5.0.Final-jbossas7.zip
192M GateIn-3.4.0.Final-jbossas5.zip
54M jboss-3.2.8.SP1.zip
60M hibernate-distribution-3.6.10.Final-dist.zip
61M hibernate-release-4.3.11.Final.zip
64M hibernate-distribution-3.5.3-Final-dist.zip
76M jboss-as-7.0.2.Final.zip
78M jboss-4.0.5.GA.zip
8.2M 10.x.zip
88M jboss-seam-2.0.2.SP1.zip
89M jboss-seam-distribution-2.3.0.Final-dist.zip
96M jboss-4.2.3.GA-jdk6.zip
2.2G total{code}
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4059:
----------------------------------
{code}
#as user
sudo su
# # as root
yum update rh-eclipse46-devstudio-10.2-0.20161005.1507.el7.x86_64.rpm
exit
# as user
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse
{code}
Timeline:
{code}
11:48:23 launch ./eclipse
11:50 eclipse opens (in under 2 mins)... but immediately, the migration assistant pops up
11:51:30 remediation starts
11:52 remediation 6/15
11:52:45 remediation 11/15
11:53:30 remediation done
(15 secs to review and click through to Finish)
11:54:30 Installing Software dialog appears
11:55:20 83%
11:57:00 83%
11:58:34 prompted to restart eclipse
12:05:51 Eclipse *finally* opens, ready to use{code}
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months