March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24083. ------------------------------ Vedified in JBT 4.4.4.AM2. Closing. > Debug NodeJS app is broken - Failed to connect to Standalone V8 VM > ------------------------------------------------------------------ > > Key: JBIDE-24083 > URL: https://issues.jboss.org/browse/JBIDE-24083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Assignee: Andre Dietisheim > Priority: Critical > Labels: regression > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: jbide-23961-restart-1.png > > > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1067) Clean update site files for stable/development/staging branch

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1067?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1067: ------------------------------------------ [~pleacu], since we released 10.2.0.GA you can now delete 10.2.0.GA from the staging branch > Clean update site files for stable/development/staging branch > ------------------------------------------------------------- > > Key: JBTIS-1067 > URL: https://issues.jboss.org/browse/JBTIS-1067 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Please clean update site files in stable/development/staging branch so that there are only html and p2 files at > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/ > {code} > and all binaries are in relevant folders such as > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/10.1.0.GA/ > {code} > Moreover, delete obsolete files from the branch 'staging'. By obsolete files I mean the following > || What we are working on? || Obsolete files || Files I'd like to keep || > | 10.2.0 | 10.0.CR1, 10.0.GA, 10.1.0.CRx, 10.1.0.GA | 10.2.0.CR1, 10.2.0.GA| > EDIT: the branch 'staging' should be cleaned after each official release (once a GA build is publicly available) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4283) migrate devstudio_10.0.neon jobs to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4283?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4283: ----------------------------- Fix Version/s: 10.x (was: 10.4.0.AM2) > migrate devstudio_10.0.neon jobs to CCI > --------------------------------------- > > Key: JBDS-4283 > URL: https://issues.jboss.org/browse/JBDS-4283 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > Migrate all jobs in this view to CCI: > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23017: ------------------------------- Labels: releasework (was: ) > use sshfs to speed up publishing process > ----------------------------------------- > > Key: JBIDE-23017 > URL: https://issues.jboss.org/browse/JBIDE-23017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.4.AM2, 4.4.4.Final > > Attachments: staging-times.png > > > Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org. > If we could simply copy bits over sshfs, the process might be a lot faster than these times: > {code} > JBT coretests 1.1G: 59m20 > JBT core 1.2G: 64m23 > devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13 > devstudio (copy from local to www.qa) 3.1G: 6mins(?) > {code} > To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23678. -------------------------------- Resolution: Done Remediation is no longer required as to 4.4.4.AM2, since there's a new version of webtools in Neon.3. > remediation required installing jbosstools 4.4.3.AM1 on Neon.2 > -------------------------------------------------------------- > > Key: JBIDE-23678 > URL: https://issues.jboss.org/browse/JBIDE-23678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png > > > Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2. > Install manifest contains: > * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions), > * 1.6.201 (2 versions), and > * 2.0.200 (1 version) - *total 7 references*! > Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4295: ------------------------------- Fix Version/s: 10.4.0.AM3 (was: 10.4.0.AM2) > Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top > ----------------------------------------------------------------------------------------------- > > Key: JBDS-4295 > URL: https://issues.jboss.org/browse/JBDS-4295 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.AM3 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM on RHEL7 via the RHSCL yum repo [1] & the devstudio yum repo [2]. This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install rh-eclipse46-devstudio > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" [3] for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * RPM URL (snapshot/staging/stable) [2] > * RHSCL URL[1] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [3] for re-running if something fails > [1] http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... or similar > [2] https://devstudio.jboss.com/static/10.0/stable/rpms/x86_64/ or https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/rpms/10.4.0/x86_64/ > [3] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4263: ------------------------------- Fix Version/s: 10.4.0.AM3 (was: 10.4.0.AM2) > Problems after install from Red Hat Central into rh-eclipse46-devstudio > ----------------------------------------------------------------------- > > Key: JBDS-4263 > URL: https://issues.jboss.org/browse/JBDS-4263 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.3.0.AM2 > Reporter: Nick Boldt > Assignee: Lukáš Valach > Fix For: 10.4.0.AM3 > > Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt > > > The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23723) Windows 10 x86 on CentralCI

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23723?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23723: --------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Windows 10 x86 on CentralCI > --------------------------- > > Key: JBIDE-23723 > URL: https://issues.jboss.org/browse/JBIDE-23723 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM3 > > > Create Windows 10 x86 image on CentralCI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4296: ------------------------------- Fix Version/s: 10.4.0.AM3 (was: 10.4.0.AM2) > Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4296 > URL: https://issues.jboss.org/browse/JBDS-4296 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests, rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.AM3 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). > This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install devstudio from installer jar > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * installer jar URL (snapshot/staging/stable) [0] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [1] for re-running if something fails > [0] https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon... or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA... > [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23725) Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23725?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23725: --------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23725 > URL: https://issues.jboss.org/browse/JBIDE-23725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM3 > > > Automate test JBDS-5892 Bean discovery in explicit and implicit archives is supported (CDI1.1+) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 March 2017