Affects: Release Notes Date of First Response: 2010-03-31 11:05:52 securitylevel_name: Public In the following test run on Hudson, the Drools test suite revealed some problems in running with IBM JDK 6: http://hudson.qa.jboss.com/hudson/view/BRMS/job/brms-rules-matrix/20/ (see the ibm16 column) Some of the listed failures are to be expected, so there is a (much shorter) list of those that only occur on IBM JDK 6: >>><<< org.drools.base.BaseClassFieldAccessorFactoryTest.testAbstract >>><<< org.drools.guvnor.client.modeldriven.SuggestionCompletionEngineTest(ECLIPSE).testCompletions >>><<< org.drools.guvnor.client.modeldriven.SuggestionCompletionEngineTest(JANINO).testCompletions >>><<< org.drools.integrationtests.ProcessMarchallingTest(ECLIPSE).test3 >>><<< org.drools.integrationtests.ProcessMarchallingTest(JANINO).test3 >>><<< org.drools.integrationtests.TruthMaintenanceTest(ECLIPSE).testLogicalInsertionsDynamicRule >>><<< org.drools.integrationtests.TruthMaintenanceTest(JANINO).testLogicalInsertionsDynamicRule
Link: Added: This issue depends JBRULES-2464
We need to document all issues we find for BRMS 5.0.2.
Affects: Added: [Release Notes]
Assigning tickets to Toni as he handles BRMS issues AFAIK. I handle core/compiler/fusion issues.
Release Notes Text: Added: test
Release Notes Text: Removed: test
Release Notes Docs Status: Added: Not Yet Documented Writer: Added: dlesage
This is not a blocker for BRMS 5.1.0, moving to future
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Needs release note
Hi, Please provide release notes information. If this was fixed in 5.2 I need Cause, Consequence, Fix and Result, if it was not fixed in 5.2 please say so.
This was not fixed in 5.2.0, the current test failures with IBM JDK are: >>> org.drools.base.BaseClassFieldAccessorFactoryTest.testAbstract >>> org.drools.camel.component.XStreamBatchExecutionTest.testInsertElementsWithReturnObjects >>> org.drools.camel.component.XStreamBatchExecutionTest.testQuery >>> org.drools.integrationtests.TruthMaintenanceTest.testLogicalInsertionsDynamicRule >>> org.drools.runtime.pipeline.impl.XStreamBatchExecutionTest.testInsertElementsWithReturnObjects >>> org.drools.runtime.pipeline.impl.XStreamBatchExecutionTest.testQuery >>> org.drools.util.debug.SessionInspectorTest.testGetSessionInfoWithCustomTemplate >>> org.jbpm.bpmn2.SimpleBPMNProcessTest.testExclusiveSplitXPathAdvanced >>> org.jbpm.integrationtests.ProcessMarshallingTest.test3 Please note that although some disappeared, new ones appeared instead.
Thanks Lukáš, The test results are no longer available at the linked location[1], is it possible that content is still online, or a link to the new test results exists? From the description of the bug it is hard to know what exactly is being tested. Thanks Lee [1]http://hudson.qa.jboss.com/hudson/view/BRMS/job/brms-rules-matrix/20/
The new test results are at the following location for the moment: https://hudson.qa.jboss.com/hudson/view/BRMS/job/brms-rules-matrix-new/jdk=ibm16,label=RHEL5_x86/lastCompletedBuild/testReport/ After further inspection, it's been identified that only these are actual test failures caused by IBM JDK: >>> org.drools.integrationtests.TruthMaintenanceTest.testLogicalInsertionsDynamicRule>>> org.drools.runtime.pipeline.impl.XStreamBatchExecutionTest.testInsertElementsWithReturnObjects >>> org.drools.util.debug.SessionInspectorTest.testGetSessionInfoWithCustomTemplate As a side note - since we don't allow customers to build the binaries from source, I think that these failures need to be documented. Customers will never see them in any of their supported use cases.
Should that read 'I *don't* think that these failures need to be documented'? (I accidentally negate my meaning all the time like this :) ) If so I agree, and will remove the release required status. thanks Lukáš
^^ should read, 'Thanks Lukáš'
(In reply to comment #14) > Should that read 'I *don't* think that these failures need to be documented'? > (I accidentally negate my meaning all the time like this :) ) Absolutely correct, "I don't think". It's still early in the morning here, my apologies. :-)
This is not failing any Guvnor tests any more. So assigned to Edson.
Deleted Technical Notes Contents. Old Contents: Needs release note
Tests fixed. Most of the problems were due to tests relying on ordering of some things like the result of Class.getMethods() method, that can vary between different JVMs.
I also fixed incompatibilities with ibm jdk caused by MVEL.
Mario Fusco <mario.fusco> updated the status of jira JBRULES-2464 to Resolved
Mario Fusco <mario.fusco> made a comment on jira JBRULES-2464 The problems were caused by some MVEL incompatibilities with the IBM JDK. I fixed them.
Update status to ON_QA. Please verify them against ER6.
VERIFIED on ER6.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.