April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24379: ------------------------------- Priority: Blocker (was: Major) > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Priority: Blocker > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24378) intermittent test failure due to ResolverProjectNature2 ?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24378: ---------------------------------- Summary: intermittent test failure due to ResolverProjectNature2 ? Key: JBIDE-24378 URL: https://issues.jboss.org/browse/JBIDE-24378 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt Some jbosstools-base builds are failing (after 40 min timeout is elapsed) with this error: {code} 03:39:52 [INFO] org.jboss.tools.common.el.core.test ................ FAILURE [40:00 min] 03:39:52 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.common.el.core.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] !MESSAGE org.jboss.tools.common.el.core.test.resolver.ResolverProjectNature2 must be instance of org.jboss.tools.common.el.core.resolver.ELResolver{code} Yet it doesn't appear this 2nd project nature contributes any actual tests. Best I can find is: ELResolverFactory1 -> ResolverProjectNature1 (but not 2) So... where in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... does this project nature actually contribute anything to tests? Could we just remove it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24378) intermittent test failure due to ResolverProjectNature2 ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24378?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24378: ------------------------------- Fix Version/s: 4.5.0.AM1 > intermittent test failure due to ResolverProjectNature2 ? > --------------------------------------------------------- > > Key: JBIDE-24378 > URL: https://issues.jboss.org/browse/JBIDE-24378 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > > Some jbosstools-base builds are failing (after 40 min timeout is elapsed) with this error: > {code} > 03:39:52 [INFO] org.jboss.tools.common.el.core.test ................ FAILURE [40:00 min] > 03:39:52 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.common.el.core.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > !MESSAGE org.jboss.tools.common.el.core.test.resolver.ResolverProjectNature2 must be instance of org.jboss.tools.common.el.core.resolver.ELResolver{code} > Yet it doesn't appear this 2nd project nature contributes any actual tests. > Best I can find is: > ELResolverFactory1 -> ResolverProjectNature1 (but not 2) > So... where in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... does this project nature actually contribute anything to tests? > Could we just remove it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24378) intermittent test failure due to ResolverProjectNature2 ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24378?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24378: ---------------------------------- Assignee: Jeff MAURY > intermittent test failure due to ResolverProjectNature2 ? > --------------------------------------------------------- > > Key: JBIDE-24378 > URL: https://issues.jboss.org/browse/JBIDE-24378 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > > Some jbosstools-base builds are failing (after 40 min timeout is elapsed) with this error: > {code} > 03:39:52 [INFO] org.jboss.tools.common.el.core.test ................ FAILURE [40:00 min] > 03:39:52 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.common.el.core.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > !MESSAGE org.jboss.tools.common.el.core.test.resolver.ResolverProjectNature2 must be instance of org.jboss.tools.common.el.core.resolver.ELResolver{code} > Yet it doesn't appear this 2nd project nature contributes any actual tests. > Best I can find is: > ELResolverFactory1 -> ResolverProjectNature1 (but not 2) > So... where in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... does this project nature actually contribute anything to tests? > Could we just remove it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24355) OpenShift New and Noteworthy for 4.4.4.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24355?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24355: ---------------------------------- Assignee: Jeff MAURY (was: Andre Dietisheim) > OpenShift New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24355 > URL: https://issues.jboss.org/browse/JBIDE-24355 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for OpenShift 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of OpenShift, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4233. ------------------------------ Fix Version/s: 10.4.0.GA Resolution: Done Done (except for 10.4.x jobs). > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.4.0.GA, 11.0.0.AM1 > > Attachments: CCI-installed-plugins-Jenkins-1.609.3-1_list.txt > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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: ----------------------------- Priority: Optional (was: Major) > 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: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 10.x > > > Migrate all jobs in this view to CCI: > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > (If required.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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: ----------------------------- Description: Migrate all jobs in this view to CCI: https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... (If required.) was: Migrate all jobs in this view to CCI: https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > 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: 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/... > (If required.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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: ----------------------------- Parent: (was: JBDS-4233) Issue Type: Task (was: Sub-task) > 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: 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23623. ------------------------------ Resolution: Done > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: jira.txt, prepare-am1.txt, run.04262017.log, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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