June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-24) [Artemis 2.x Upgrade] Last value queues do not work

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFWIP-24?page=com.atlassian.jira.plugin.s... ] Jiri Ondrusek resolved WFWIP-24. -------------------------------- Resolution: Resolved at Apache Already fixed in artemis (2.6.0) - see https://issues.apache.org/jira/browse/ARTEMIS-1766 > [Artemis 2.x Upgrade] Last value queues do not work > --------------------------------------------------- > > Key: WFWIP-24 > URL: https://issues.jboss.org/browse/WFWIP-24 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Martin Styk > Assignee: Jiri Ondrusek > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Last value queues are not working as expected. > # Set {{last-value-queue="true"}} for an address settings {{#}} > # Send 10 messages with {{message.setStringProperty("_AMQ_LVQ_NAME", "myProperty");}} > # Receiver receives 10 messages. (it is expected to receive the single message) > This looks like broker related regression against Artemis 1.5. > Wildfly: {{https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_with_prefix}} (c692e8327023f9bc40699a6863b4197cc7c1b3c8) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2625) Executable model - AccumulateTest and other tests fail with the model

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2625?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2625: ---------------------------------- Description: Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: - AccumulateTest - AlphaNetworkModifyTest - AlphaTest - AnnotationsTest - ArrayTest - BackwardChainingTest PR with tests: https://github.com/kiegroup/drools/pull/1941 was: Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: - AccumulateTest - AlphaNetworkModifyTest - AlphaTest - AnnotationsTest - ArrayTest - BackwardChainingTest > Executable model - AccumulateTest and other tests fail with the model > --------------------------------------------------------------------- > > Key: DROOLS-2625 > URL: https://issues.jboss.org/browse/DROOLS-2625 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: > - AccumulateTest > - AlphaNetworkModifyTest > - AlphaTest > - AnnotationsTest > - ArrayTest > - BackwardChainingTest > PR with tests: https://github.com/kiegroup/drools/pull/1941 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2625) Executable model - AccumulateTest and other tests fail with the model

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2625: ------------------------------------- Summary: Executable model - AccumulateTest and other tests fail with the model Key: DROOLS-2625 URL: https://issues.jboss.org/browse/DROOLS-2625 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: - AccumulateTest - AlphaNetworkModifyTest - AlphaTest - AnnotationsTest - ArrayTest - BackwardChainingTest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3915) Do not deploy test suite modules

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3915?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3915: -------------------------------- Priority: Minor (was: Major) > Do not deploy test suite modules > -------------------------------- > > Key: WFCORE-3915 > URL: https://issues.jboss.org/browse/WFCORE-3915 > Project: WildFly Core > Issue Type: Bug > Components: Build System > Affects Versions: 5.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > 3 modules inside Core test suite uses wildfly-core-parent as their parent instead of wildfly-core-testsuite: > * shared > * test-runner > * vault-test-feature-pack > One consequence is that when Core is released, these 3 artifacts are included in the release while they should not be (no other test suite modules is part of a release) > They do not use wildfly-core-testsuite for good reason (cyclic dependencies, etc.) but they must be flagged to skip maven deployment with maven.deploy.skip set to true. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3915) Do not deploy test suite modules

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3915?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3915: -------------------------------- Description: 3 modules inside Core test suite uses wildfly-core-parent as their parent instead of wildfly-core-testsuite: * shared * test-runner * vault-test-feature-pack One consequence is that when Core is released, these 3 artifacts are included in the release while they should not be (no other test suite modules is part of a release) They do not use wildfly-core-testsuite for good reason (cyclic dependencies, etc.) but they must be flagged to skip maven deployment with maven.deploy.skip set to true. was: 3 modules inside Core test suite uses wildfly-core-parent as their parent instead of wildfly-core-testsuite: * shared * test-runner * vault-test-feature-pack One consequence is that when Core is released, these 3 artifacts are included in the release while they should not be (no other test suite modules is part of a release) > Do not deploy test suite modules > -------------------------------- > > Key: WFCORE-3915 > URL: https://issues.jboss.org/browse/WFCORE-3915 > Project: WildFly Core > Issue Type: Bug > Components: Build System > Affects Versions: 5.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > 3 modules inside Core test suite uses wildfly-core-parent as their parent instead of wildfly-core-testsuite: > * shared > * test-runner > * vault-test-feature-pack > One consequence is that when Core is released, these 3 artifacts are included in the release while they should not be (no other test suite modules is part of a release) > They do not use wildfly-core-testsuite for good reason (cyclic dependencies, etc.) but they must be flagged to skip maven deployment with maven.deploy.skip set to true. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3915) Do not deploy test suite modules

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3915?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3915: -------------------------------- Summary: Do not deploy test suite modules (was: Fix test suite modules parent relation) > Do not deploy test suite modules > -------------------------------- > > Key: WFCORE-3915 > URL: https://issues.jboss.org/browse/WFCORE-3915 > Project: WildFly Core > Issue Type: Bug > Components: Build System > Affects Versions: 5.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > 3 modules inside Core test suite uses wildfly-core-parent as their parent instead of wildfly-core-testsuite: > * shared > * test-runner > * vault-test-feature-pack > One consequence is that when Core is released, these 3 artifacts are included in the release while they should not be (no other test suite modules is part of a release) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2624) Fix jacoco problem for guided rule module

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2624: ----------------------------------- Summary: Fix jacoco problem for guided rule module Key: DROOLS-2624 URL: https://issues.jboss.org/browse/DROOLS-2624 Project: Drools Issue Type: Task Components: Guided Rule Editor Reporter: Jozef Marko Assignee: Jozef Marko Jacoco for the guided rule module can't be measured: {code:shell} $ mvn clean verify -Dcode-coverage ... Tests in error: RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... RuleModellerTest.setUp:83 » ExceptionInInitializer RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... ConnectivesTest.testConnectiveOperatorsInteger:50 » NoClassDefFound Could not ... ConnectivesTest.testConnectiveOperatorsString:40 » ExceptionInInitializer FactPatternWidgetTest.setUp:77 » ExceptionInInitializer FactPatternWidgetTest.setUp:77 » NoClassDefFound Could not initialize class or... AddAttributeWidgetTest.org.drools.workbench.screens.guided.rule.client.widget.attribute.AddAttributeWidgetTest » Runtime GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... GuidedRuleAttributeSelectorPopupTest.setUp:55 » ExceptionInInitializer {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2624) Fix jacoco problem for guided rule module

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2624?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2624: -------------------------------- Affects Version/s: 7.8.0.Final > Fix jacoco problem for guided rule module > ----------------------------------------- > > Key: DROOLS-2624 > URL: https://issues.jboss.org/browse/DROOLS-2624 > Project: Drools > Issue Type: Task > Components: Guided Rule Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > Jacoco for the guided rule module can't be measured: > {code:shell} > $ mvn clean verify -Dcode-coverage > ... > Tests in error: > RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... > RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... > RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... > RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... > RuleModellerTest.setUp:83 » ExceptionInInitializer > RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... > RuleModellerTest.setUp:83 » NoClassDefFound Could not initialize class org.dro... > ConnectivesTest.testConnectiveOperatorsInteger:50 » NoClassDefFound Could not ... > ConnectivesTest.testConnectiveOperatorsString:40 » ExceptionInInitializer > FactPatternWidgetTest.setUp:77 » ExceptionInInitializer > FactPatternWidgetTest.setUp:77 » NoClassDefFound Could not initialize class or... > AddAttributeWidgetTest.org.drools.workbench.screens.guided.rule.client.widget.attribute.AddAttributeWidgetTest » Runtime > GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... > GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... > GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... > GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... > GuidedRuleAttributeSelectorPopupTest.setUp:55 » NoClassDefFound Could not init... > GuidedRuleAttributeSelectorPopupTest.setUp:55 » ExceptionInInitializer > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-284) Fix Update sites on jenkins2

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-284: ----------------------------------- Summary: Fix Update sites on jenkins2 Key: SWSQE-284 URL: https://issues.jboss.org/browse/SWSQE-284 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Filip Brychta Update sites on jenkins2 contain http://ci-ops-jenkins-update-site.rhev-ci-vms.eng.rdu2.redhat.com/update-... as a default update side which is not working. Default one was overwritten by this. We need to add back default one and fix this redhat update site. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-263) Kiali Istio Checker Job may not be working

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-263?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-263. -------------------------------- Resolution: Done > Kiali Istio Checker Job may not be working > ------------------------------------------- > > Key: SWSQE-263 > URL: https://issues.jboss.org/browse/SWSQE-263 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Sunil kondkar > > I think Kiali Istio Checker is not running fine > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Running > Current istio-ca pod status : Running > scripts/kiali/testscript.sh: line 55: [: too many arguments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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

jboss-jira June 2018