Hide Forgot
Date of First Response: 2007-10-31 18:05:58 project_key: SOA drools-compiler has a large range of integration tests, attempts should be made to execute all of these.
yes, we're working on this with AlexK
Link: Added: This issue is related to JBQA-852
please see http://hudson.qa.jboss.com/hudson/view/SOA/job/drools-4.0.2_SOA-4.2_branch/ Mark, can you verify we run all necessary tests against the SOA-P drools bits? http://hudson.qa.jboss.com/hudson/view/SOA/job/drools-4.0.2_SOA-4.2_branch/64/testReport/
I'm going to assign fernando for 2 weeks full time to the soa platform stuff, he will do all remaining tests and verify this for you.
what do you mean by "all remaining tests", can you point to any jiras? Are these new tests? What kind of tests? BTW, in my comment above, by "all necessary tests", I meant all necessary tests included in the native drools testsuite.
Hi Mark, any comments on this jira?
Fernando will be doing stuff like JBossWS testing. As far as I can tell you are not running anything against SOA-P, you are just running a drools branch that we made for SOA-P, so I'm not sure what it is you wish me to confirm? Its executing 1408 tests compared to 1968 in 4.0.x - but as far as I can tell that is only due to SOA-P not build eclipse.
My fault! The URL above is a hudson job we set up only to compile tests jars needed for the drools testsuite. http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite-single/82/testReport/ is the job, which runs the testsuite from http://anonsvn.labs.jboss.com/labs/jbossrules/branches/Branch_4_0_2_SOA_4_2/ against the drools bits shipped with SOA-P.
Below is an URL to results for running the testsuite against the current SOA-P bits: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite-single/93/testReport/ All errors will go away, when we use finally the correct drools bits in SOA-P, beside two issues which come up only when using JANINO: Could you please have a look at them? http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite-single/93/testReport/org.drools.compiler/Java5Test(JANINO)/testJava5Rule/ http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite-single/93/testReport/org.drools.integrationtests/MiscTest(JANINO)/testWithInvalidRule/ Thanks
According the latest test the configuration isn't founding janino library, could someone take a look or help me with? http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite-single/95/
Jarek, I found the problem, both ESB and EAP are using an old mvel version mvel14-1.2rc4rv908.jar when drools depends of latest mvel14-1.2.8.jar Fernando
Link: Added: This issue depends SOA-243
Waiting for http://jira.jboss.com/jira/browse/SOA-242 and http://jira.jboss.com/jira/browse/SOA-243 to finish this test Locally after update these libs tests execute with no erros
Java5Test is Fixed, PackageBuilder should receive the configuration as a constructor parameter To test against eclipse, janino doesn't support J2SE 5.0: Enhanced FOR loop MiscTest.testWithInvalidRule: I found a problem in janino when we use $variable, janino tries to tokenize as an innerClass, will open a ticket in janino's jira
Nice! http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite-single/109/testReport/ I'm closing this jira.
A run on a win box shows 4 errors: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/8/label=Win2k3_x86/testReport/ However they seem to be transient, the next run showed only 3 of those 4 errors: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/label=Win2k3_x86/9/testReport/
RHEL4 once failed http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/label=RHEL4_x86/9/testReport/ RHEL5 once failed http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/label=RHEL5_x86/10/testReport/ Odd that it seems issue is not much hardware dependent: The RHEL5 tests failed once on 2 hyperthreading CPU box and didn't on HW similar to that of the windows machine (2 dual-core CPUs) The RHEL4 tests failed once on a vmware guest and passed many times on vmware guests and a dual CPU box (single-core hyper-threading). The windows tests always failed on the 2 CPU dual-core box (not tested on other HW).
This looks like a (obviously intermittent ) race condition with the mvel dialect (I have seen it sometimes on my laptop).
yes I think so too. Mike Brock says it's the enhancements that I made to MVEL for the foreach loop that might be it, but I have no idea how to fix it. Now that it's showing up in SOA-P hopefully he'll look over it for us.
OK apparently there is a new MVEL version out that fixes this (thanks to Mike Brock). 1.2.20.
cbrock fixed mvel so variables cannot be defined twice, that test has invalid MVEL code that wasn't picked up on before I'm reviewing test sources and will check it again
According Jaroslaw we still have thread safety issues on windows machines http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/17/label=Win2k3_x86/testReport/
the variables cannot be defined twice was corrected on the drools-soa branch
What is the status of this issue?
Will provide a status today... there are some hudson issues which needs to be fixed.
status for RC1: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/26/ org.drools.integrationtests.PackageBuilderThreadSafetyTest is still failing on windows: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/26/label=Win2k3_x86/testReport/org.drools.integrationtests/PackageBuilderThreadSafetyTest(JANINO)/testThreadSafetyEclipse http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/26/label=Win2k3_x86/testReport/org.drools.integrationtests/PackageBuilderThreadSafetyTest(ECLIPSE)/testThreadSafetyEclipse
Is there a JIRA for the failed tests?
There are a couple of them, SOA-336, SOA-337 and some others which fix the errors reported in hudson. AFAIK, the latest errors in testThreadSafetyEclipse have also been fixed (CR2), don't know the jira, maybe Fernando will know.
Link: Added: This issue depends SOA-336
According to Fernando - these are the ONLY TWO bugs resulting: SOA-336, SOA-337
about soa-45 the issue was on thread safety issue that cbrock fixes with the latest mvel version with the new version we must update the mvel templates on drools, that what those issues are related to
status for CR2: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/28/ org.drools.integrationtests.PackageBuilderThreadSafetyTest is still failing on windows: http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-rules-testsuite/label=Win2k3_x86/28/testReport/
Link: Added: This issue is related to SOA-497
Fernando no longer works for us.
This can be closed, see http://intranet.corp.redhat.com/ic/intranet/SOAP42JBossRulesTestsuite.html for detailed description of all drools testsuites. PackageBuilderThreadSafetyTest is fixed, all other issues are logged in jira.
Running in Hudson