Red Hat Bugzilla – Bug 1298579
NPE removing a rule that contains a subnetwork
Last modified: 2016-04-01 07:58:45 EDT
Created attachment 1114800 [details]
Description of problem:
BZ for corresponding JIRA DROOLS-1025
Version-Release number of selected component (if applicable):
Steps to Reproduce:
In order to reproduce issue, I suggest you to download PATCH binaries from
Extract them to your file system, and then execute:
$ mvn install:install-file -Dfile=drools-core-6.3.0.Final-redhat-5-BZ-1292828.jar -Dsources=drools-core-6.3.0.Final-redhat-5-BZ-1292828-sources.jar -DgroupId=org.drools -DartifactId=drools-core -Dversion=6.3.0.Final-redhat-5-BZ-1292828 -DpomFile=drools-core-6.3.0.Final-redhat-5-BZ-1292828.pom -Dpackaging=jar
$ mvn install:install-file -Dfile=drools-compiler-6.3.0.Final-redhat-5-BZ-1292828.jar -Dsources=drools-compiler-6.3.0.Final-redhat-5-BZ-1292828-sources.jar -DgroupId=org.drools -DartifactId=drools-compiler -Dversion=6.3.0.Final-redhat-5-BZ-1292828 -DpomFile=drools-compiler-6.3.0.Final-redhat-5-BZ-1292828.pom -Dpackaging=jar
$ mvn install:install-file -Dfile=drools-reteoo-6.3.0.Final-redhat-5-BZ-1292828.jar -Dsources=drools-reteoo-6.3.0.Final-redhat-5-BZ-1292828-sources.jar -DgroupId=org.drools -DartifactId=drools-reteoo -Dversion=6.3.0.Final-redhat-5-BZ-1292828 -DpomFile=drools-reteoo-6.3.0.Final-redhat-5-BZ-1292828.pom -Dpackaging=jar
However, it seems that the tests fails in a same fashion with 6.4.0-SNAPSHOT version too.
If I test this with "6.3.0.Final-redhat-5" version then only 1 test fails out of three, so it may be related directly to the changes made BZ-1292828
all JUnit test fails
none of the test fails
Fixed by https://github.com/droolsjbpm/drools/commit/460056cc3 and https://github.com/droolsjbpm/drools/commit/8d52a6a34
Fixed by https://github.com/droolsjbpm/drools/commit/d1cdd567c
Ryan, I cannot find the last commit (https://github.com/droolsjbpm/drools/commit/d1cdd567c) in ER1, could you please double check if it is really missing?
The cutting date is March 8, so you are correct that the second commit wasn't in the ER1 tag.
My filter didn't work well for this case since there 2 "MODIFIED" date and the 2nd one didn't catch ER1 tag.
Apology for all the inconvinience, Marek!
(Moving back to MODIFIED)
Ryan, no problem at all, thanks for quick confirmation!
Verified by new tests from PRs and by running reproducer.