-
Bug
-
Resolution: Done
-
Major
-
7.46.0.Final
-
None
-
2021 Week 13-15 (from Mar 29), 2021 Week 16-18 (from Apr 19), 2021 Week 19-21 (from May 10), 2021 Week 22-24 (from May 31), 2021 Week 25-27 (from Jun 21), 2021 Week 28-30 (from Jul 12), 2021 Week 31-33 (from Aug 2), 2021 Week 34-36 (from Aug 23)
-
5
-
Undefined
-
NEW
-
NEW
-
---
-
---
org.drools.mvel.integrationtests.NamedConsequencesTest in test-compiler-integration fails with some tests when executable-model is enabled. See TODO comment in the test class. Once fixed (or the test failure is justified), we can remove the TODO comment and let the test run with executable-model.
Currently, executable-model is disabled:
// TODO: .... return TestParametersUtil.getKieBaseCloudConfigurations(false);
If the test failure contains multiple bugs, we may split this JIRA into multiple JIRAs.
- incorporates
-
DROOLS-6289 NamedConsequencesTest issues
- Closed
-
DROOLS-6376 NamedConsequence if-else in a row with exec-model
- Closed
-
DROOLS-6386 BitMask is not generated for modify in named consequence with exec-model
- Closed
-
DROOLS-6408 NamedConsequence multiple if after eval with exec-model
- Closed
-
DROOLS-6409 if (true) for conditional named consequence fails with exec-model
- Closed
-
DROOLS-6290 NamedConsequences inside OR
- Pull Request Sent
- is related to
-
DROOLS-5729 Reorganize drools unit tests
- Coding In Progress