[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 edited comment on DROOLS-2426 at 4/3/18 9:53 AM:
---------------------------------------------------------------
Ok nevermind, I'm blind, there is an inherited partitioned agenda with partitionId. So don't mind my previous comment.
However I think I found the problem (really this time:) ). The problem is that the master agenda expires fact handle before other agendas gets time to process propagations created based on this fact handle. When I comment this out [1], the test works.
I think there might be some sort of callback mechanism for fact handle expiration, because there must be guaranteed that each partitioned agenda have time to process all propagations related to a fact handle (a sort of synchronization on fact handle expiration).
[1] https://github.com/kiegroup/drools/blob/91cb991a4db283ac00eaa2e16d606d722...
was (Author: tzimanyi):
Ok nevermind, I'm blind, there is an inherited partitioned agenda with partitionId. So don't mind my previous comment.
However I think I found the problem (really this time:) ). The problem is that the master agenda expires fact handle before other agendas gets time to process activations created based on this fact handle. When I comment this out [1], the test works.
I think there might be some sort of callback mechanism for fact handle expiration, because there must be guaranteed that each partitioned agenda have time to process all propagations related to a fact handle (a sort of synchronization on fact handle expiration).
[1] https://github.com/kiegroup/drools/blob/91cb991a4db283ac00eaa2e16d606d722...
> 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. One idea what happens is that one agenda thread expires events from second agenda on some race condition. But that is a first guess after looking at the code.
> Steps to reproduce:
> 1. Change the number of parallel partitions to 2 here [1]
> 2. Rebuild drools-core
> 3. 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)
6 years, 10 months
[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 commented on DROOLS-2426:
---------------------------------------
Ok nevermind, I'm blind, there is an inherited partitioned agenda with partitionId. So don't mind my previous comment.
However I think I found the problem (really this time:) ). The problem is that the master agenda expires fact handle before other agendas gets time to process activations created based on this fact handle. When I comment this out [1], the test works.
I think there might be some sort of callback mechanism for fact handle expiration, because there must be guaranteed that each partitioned agenda have time to process all propagations related to a fact handle (a sort of synchronization on fact handle expiration).
[1] https://github.com/kiegroup/drools/blob/91cb991a4db283ac00eaa2e16d606d722...
> 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. One idea what happens is that one agenda thread expires events from second agenda on some race condition. But that is a first guess after looking at the code.
> Steps to reproduce:
> 1. Change the number of parallel partitions to 2 here [1]
> 2. Rebuild drools-core
> 3. 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)
6 years, 10 months
[JBoss JIRA] (WFCORE-3596) further improve the permissions mapping configuration model to be manageable to by a tool
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3596?page=com.atlassian.jira.plugi... ]
Farah Juma reassigned WFCORE-3596:
----------------------------------
Assignee: Farah Juma
> further improve the permissions mapping configuration model to be manageable to by a tool
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-3596
> URL: https://issues.jboss.org/browse/WFCORE-3596
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Affects Versions: 4.0.0.Alpha10
> Reporter: Alexey Loubyansky
> Assignee: Farah Juma
> Priority: Critical
>
> The current configuration model for mapping permissions does not appear to be manageable by a tool that is trying to add/remove permissions based on the presence/absence of a specific subsystem.
> This is a critical issue for the provisioning mechanism which is not only producing the default configuration that could be simple enough but also allows the user to customize the default configuration and then preserve the user changes after applying a version update or a patch.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (SWSQE-112) Document configuration of openshift production cluster
by Filip Brychta (JIRA)
[ https://issues.jboss.org/browse/SWSQE-112?page=com.atlassian.jira.plugin.... ]
Filip Brychta updated SWSQE-112:
--------------------------------
Description:
We need mojo page with full description of our openshift production cluster which should include:
* used blades
* OS version
* description of all necessary accounts and permissions (for jenkins, jenkins slaves,...)
* description of persistence storage
* ...
was:
We need mojo page with full description of our openshift production cluster which should include:
* used blades
* OS version
* description of all necessary accounts and permissions (for jenkins, jenkins slaves,...)
* ...
> Document configuration of openshift production cluster
> ------------------------------------------------------
>
> Key: SWSQE-112
> URL: https://issues.jboss.org/browse/SWSQE-112
> Project: Kiali QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Michael Foley
>
> We need mojo page with full description of our openshift production cluster which should include:
> * used blades
> * OS version
> * description of all necessary accounts and permissions (for jenkins, jenkins slaves,...)
> * description of persistence storage
> * ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (WFCORE-3725) further improve the permissions mapping configuration model to be manageable to by a tool
by Farah Juma (JIRA)
Farah Juma created WFCORE-3725:
----------------------------------
Summary: further improve the permissions mapping configuration model to be manageable to by a tool
Key: WFCORE-3725
URL: https://issues.jboss.org/browse/WFCORE-3725
Project: WildFly Core
Issue Type: Task
Components: Security
Affects Versions: 4.0.0.Alpha10
Reporter: Farah Juma
Priority: Critical
The current configuration model for mapping permissions does not appear to be manageable by a tool that is trying to add/remove permissions based on the presence/absence of a specific subsystem.
This is a critical issue for the provisioning mechanism which is not only producing the default configuration that could be simple enough but also allows the user to customize the default configuration and then preserve the user changes after applying a version update or a patch.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (WFCORE-3722) WildFly Build Tools version properties is set in two different POMs
by Martin Stefanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ]
Martin Stefanko reassigned WFCORE-3722:
---------------------------------------
Assignee: Martin Stefanko
> WildFly Build Tools version properties is set in two different POMs
> -------------------------------------------------------------------
>
> Key: WFCORE-3722
> URL: https://issues.jboss.org/browse/WFCORE-3722
> Project: WildFly Core
> Issue Type: Bug
> Reporter: David Lloyd
> Assignee: Martin Stefanko
>
> {noformat}
> $ grep build-tools `find . -name pom.xml`
> ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools>
> ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools>
> ./pom.xml: <version>${version.org.wildfly.build-tools}</version>
> ./pom.xml: <version>${version.org.wildfly.build-tools}</version>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney resolved SWSQE-107.
--------------------------------
Resolution: Done
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline (Production=PR-Testing + Overnight-Testing).
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney commented on SWSQE-107:
------------------------------------
Team selected b21 as the Production Openshift cluster.
We will migrate our testing and prototyping off of b21 and on to other clusters b111/b12/OSOOS-Clusters
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline (Production=PR-Testing + Overnight-Testing).
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Kevin Earls (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Kevin Earls moved KIALI-468 to SWSQE-113:
-----------------------------------------
Project: Kiali QE (was: Kiali)
Key: SWSQE-113 (was: KIALI-468)
Workflow: classic default workflow (was: SWS Workflow)
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Filip Brychta
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months