March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-94) Set up zalenium in openshift

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-94: ---------------------------------- Summary: Set up zalenium in openshift Key: SWSQE-94 URL: https://issues.jboss.org/browse/SWSQE-94 Project: Swift Sunshine QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Michael Foley Currently we have zalenium running here http://zalenium-fbr-zal-test.openshift.jonqe.lab.eng.bos.redhat.com/ We need to: * create official team project in our production openshift * deploy zalenium there * tune the zalenium to increase performance -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2426) ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2426?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2426: ---------------------------------- Description: The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails randomly, when the machine on which it is run has smaller amount of processors (tested with 2). It fails because the engine doesn't produce expected amount of rule fires, so the test waits on a CountDownLatch. Steps to reproduce: 1. Change the number of parallel partitions to 2 here [1] 2. Run the test from PR [2] few times. [1] https://github.com/kiegroup/drools/blob/63ea870c89591dfeae1276f582d825670... [2] https://github.com/kiegroup/drools/pull/1843 was: The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails randomly, when the machine on which it is run has smaller amount of processors (tested with 2). Steps to reproduce: 1. Change the number of parallel partitions to 2 here [1] 2. Run the test from PR [1] https://github.com/kiegroup/drools/blob/63ea870c89591dfeae1276f582d825670... > ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2426 > URL: https://issues.jboss.org/browse/DROOLS-2426 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > > The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails randomly, when the machine on which it is run has smaller amount of processors (tested with 2). It fails because the engine doesn't produce expected amount of rule fires, so the test waits on a CountDownLatch. > Steps to reproduce: > 1. Change the number of parallel partitions to 2 here [1] > 2. Run the test from PR [2] few times. > [1] https://github.com/kiegroup/drools/blob/63ea870c89591dfeae1276f582d825670... > [2] https://github.com/kiegroup/drools/pull/1843 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2426) ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2426?page=com.atlassian.jira.plugi... ] Tibor Zimányi reassigned DROOLS-2426: ------------------------------------- Assignee: Mario Fusco (was: Tibor Zimányi) > ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2426 > URL: https://issues.jboss.org/browse/DROOLS-2426 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails randomly, when the machine on which it is run has smaller amount of processors (tested with 2). It fails because the engine doesn't produce expected amount of rule fires, so the test waits on a CountDownLatch. > Steps to reproduce: > 1. Change the number of parallel partitions to 2 here [1] > 2. Run the test from PR [2] few times. > [1] https://github.com/kiegroup/drools/blob/63ea870c89591dfeae1276f582d825670... > [2] https://github.com/kiegroup/drools/pull/1843 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-21) Openshift Source-2-Image Pipeline for Test Suites

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-21?page=com.atlassian.jira.plugin.s... ] Matt Mahoney closed SWSQE-21. ----------------------------- Resolution: Done > Openshift Source-2-Image Pipeline for Test Suites > ------------------------------------------------- > > Key: SWSQE-21 > URL: https://issues.jboss.org/browse/SWSQE-21 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: viet nguyen > > Configure an Openshift Source-to-Image pipline for QE test suites. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2426) ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2426?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2426: ---------------------------------- Description: The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails randomly, when the machine on which it is run has smaller amount of processors (tested with 2). Steps to reproduce: 1. Change the number of parallel partitions to 2 here [1] 2. Run the test from PR [1] https://github.com/kiegroup/drools/blob/63ea870c89591dfeae1276f582d825670... was: The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 contains a Thread.sleep() call [1] which makes the test fail on slower machines, because it lets the test execution run sooner than fireUntilHalt does all firings. [1] https://github.com/kiegroup/drools/blob/ffa6f44a10fa50f3227491968f9166b57... > ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2426 > URL: https://issues.jboss.org/browse/DROOLS-2426 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > > The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails randomly, when the machine on which it is run has smaller amount of processors (tested with 2). > Steps to reproduce: > 1. Change the number of parallel partitions to 2 here [1] > 2. Run the test from PR > [1] https://github.com/kiegroup/drools/blob/63ea870c89591dfeae1276f582d825670... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-79) Report jenkins CI result back to the community(github PR's)

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-79?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-79: ------------------------------ Sprint: SWS QE Sprint 2, Kiali QE Sprint 3 (was: SWS QE Sprint 2) > Report jenkins CI result back to the community(github PR's) > ----------------------------------------------------------- > > Key: SWSQE-79 > URL: https://issues.jboss.org/browse/SWSQE-79 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Currently, we show only pass or fail status of the suite to PR. There is no failure reason for PR from internal Jenkins job. > Sample: https://github.com/jaegertracing/jaeger-openshift/tree/master/jenkins-ci -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2420) [DMN Designer] Hit Policy Collect does not need an Aggregation function

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2420?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2420: -------------------------------- Description: Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" h2. Acceptance test # After saving and reopening is user able to achieve Collect hit policy (/) ## with aggregating function ## without aggregating function # After saving and reopening is user able to change (/) ## From any collect hit policy to non collect hit policy ## From non collect hit policy to collect hit policy # Change of hit policy is reflected in dmn file (/) # Change of hit policy will show aggregation function just if Collect hit policy, otherwise None (/) was: Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" h2. Acceptance test # After saving and reopening is user able to achieve Collect hit policy (/) ## with aggregating function ## without aggregating function # After saving and reopening is user able to change (/) ## From any collect hit policy to non collect hit policy ## From non collect hit policy to collect hit policy # Change of hit policy is reflected in dmn file (/) # Change of hit policy will show aggregation function just if Collect hit policy, otherwise None > [DMN Designer] Hit Policy Collect does not need an Aggregation function > ----------------------------------------------------------------------- > > Key: DROOLS-2420 > URL: https://issues.jboss.org/browse/DROOLS-2420 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" > h2. Acceptance test > # After saving and reopening is user able to achieve Collect hit policy (/) > ## with aggregating function > ## without aggregating function > # After saving and reopening is user able to change (/) > ## From any collect hit policy to non collect hit policy > ## From non collect hit policy to collect hit policy > # Change of hit policy is reflected in dmn file (/) > # Change of hit policy will show aggregation function just if Collect hit policy, otherwise None (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2426) ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2426?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2426: ---------------------------------- Summary: ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors (was: ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails on slower machines) > ParallelEvaluationTest.testFireUntilHaltWithExpiration2 fails with lower amount of processors > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2426 > URL: https://issues.jboss.org/browse/DROOLS-2426 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > > The test ParallelEvaluationTest.testFireUntilHaltWithExpiration2 contains a Thread.sleep() call [1] which makes the test fail on slower machines, because it lets the test execution run sooner than fireUntilHalt does all firings. > [1] https://github.com/kiegroup/drools/blob/ffa6f44a10fa50f3227491968f9166b57... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2427) Drools @Watch not working with accumulate in code

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2427: ----------------------------------- Summary: Drools @Watch not working with accumulate in code Key: DROOLS-2427 URL: https://issues.jboss.org/browse/DROOLS-2427 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco I'm using Drools 7.6 and for some reason @watch doesn't stop the rule from reactivating itself or other rules when only the unwatched property is changed. Which results in an infinite loop. Can someone figure out what am I doing wrong? The rule: {code} package com.model import com.model.*; import java.util.List; rule "10% for 15 High-range Items" when $o: Order($lines: orderLines) @watch(!discount) Number(intValue >= 15) from accumulate( OrderLine($item: item, $q: quantity) from $lines and Item(category == Item.Category.HIGH_RANGE) from $item, sum($q) ) then modify($o) {increaseDiscount(0.10)} end {code} The model used is from the book Mastering JBoss Drools. The method increase discount has been annotated with @Modifes. The order class: {code} public class Order implements Serializable { private static final long serialVersionUID = 1L; private Long orderId; private Date date; private Customer customer; private List<OrderLine> orderLines = new ArrayList<>(); private Discount discount; public Order() { } public Long getOrderId() { return orderId; } public void setOrderId(Long orderId) { this.orderId = orderId; } public Customer getCustomer() { return customer; } public void setCustomer(Customer customer) { this.customer = customer; } public Date getDate() { return date; } public void setDate(Date date) { this.date = date; } public List<OrderLine> getOrderLines() { return orderLines; } public void setItems(List<OrderLine> orderLines) { this.orderLines = orderLines; } public double getTotal() { return this.getOrderLines().stream() .mapToDouble(item -> item.getItem().getSalePrice() * item.getQuantity()) .sum(); } public int getTotalItems() { return this.getOrderLines().stream() .mapToInt(item -> item.getQuantity()) .sum(); } @Modifies({"discount"}) public void increaseDiscount(double increase) { if (discount == null) { discount = new Discount(0.0); } discount.setPercentage(discount.getPercentage() + increase); } public Discount getDiscount() { return discount; } public double getDiscountPercentage() { return discount.getPercentage(); } public void setDiscount(Discount discount) { this.discount = discount; } } {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-21) Openshift Source-2-Image Pipeline for Test Suites

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-21?page=com.atlassian.jira.plugin.s... ] Matt Mahoney commented on SWSQE-21: ----------------------------------- At least for the foreseeable future, will not be using Source-2 Image pipeline. Thus, closing. > Openshift Source-2-Image Pipeline for Test Suites > ------------------------------------------------- > > Key: SWSQE-21 > URL: https://issues.jboss.org/browse/SWSQE-21 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: viet nguyen > > Configure an Openshift Source-to-Image pipline for QE test suites. -- 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 March 2018