[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26098:
---------------------------------------
In my opinion eclipse just crashed and so no test failures were reported, probably, so surefire just went on. Look at log: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
> Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-26098 at 7/19/18 5:19 PM:
----------------------------------------------------------------
[~nickboldt] I know that if you look at Reactor summary you can see SUCCESS at stacks.core.test, but if you would thoroughly examine console output, searching for "Building org.jboss.tools.stacks.core.test 1.4.100-SNAPSHOT" and look closer, you will see "There are test failures". And when looking here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo..., there are no stacks tests mentioned. Seems like those are just ignored if failed. No idea why are marked as SUCCESS.
was (Author: odockal):
[~nickboldt] I know that if you look at Reactor summary you can see SUCCESS at stacks.core.test, but if you will examine console output, searching for "Building org.jboss.tools.stacks.core.test 1.4.100-SNAPSHOT" and look closer, you will see "There are test failures" in that section. And when looking here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo..., there are no stacks tests mentioned. Seems like those are just ignored if failed.
> Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26098:
---------------------------------------
[~nickboldt] I know that if you look at Reactor summary you can see SUCCESS at stacks.core.test, but if you will examine console output, searching for "Building org.jboss.tools.stacks.core.test 1.4.100-SNAPSHOT" and look closer, you will see "There are test failures" in that section. And when looking here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo..., there are no stacks tests mentioned. Seems like those are just ignored if failed.
> Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26180 at 7/19/18 3:02 PM:
-------------------------------------------------------------
New TP only contains 9 dupe IUs, and is 584M on disk:
{code}
[WARNING] Found 9 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.1.1.v20180414-0329.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
was (Author: nickboldt):
New TP only contains 9 dupe IUs:
{code}
[WARNING] Found 9 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.1.1.v20180414-0329.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26180:
------------------------------------
New TP only contains 9 dupe IUs:
{code}
[WARNING] Found 9 duplicate jbosstools plugins:
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar
[WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar
[WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar
[WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar
[WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar
[WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar
[WARNING] [6] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.1.1.v20180414-0329.jar
[WARNING] [7] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
[WARNING] [8] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar
[WARNING] [9] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar
{code}
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
by Alexander Kurtakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Alexander Kurtakov commented on JBIDE-26098:
--------------------------------------------
This is too big range for me to cover. Upstream we are going to move httpcore 4.4.6 -> 4.4.9 and httpclient 4.5.2 -> 4.5.5 - these updates have nothing else but bugfixes. If you move from 4.0.x that's way bigger task to verify and it would need to be done by the one using these old versions.
> Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26098:
------------------------------------
[~odockal]I don't see test failures in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... ... what problem are you trying to fix?
> Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26098:
------------------------------------
httpcomponents changes COULD cause a problem. [~akurtako] [~mat.booth] do you know more about changes between the versions of httpclient and httpcore noted above?
> Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26098
> URL: https://issues.jboss.org/browse/JBIDE-26098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: qa
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM1
>
>
> 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results).
> 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin:
> * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change
> * org.yaml.snakeyaml; 1.10 -> 1.18
> * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5
> * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9
> * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final
> 3. Run all stacks.tests available (only one test class was run)
> 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months