[julien1]

correct, it was a mistake from Chris that did not update his test case according to other changes he did 2 days ago

I fixed it.

Testsuite build failed because of deploymet issue with wsrp-producer.

2007-02-06 11:06:35,628 INFO [org.jboss.system.ServiceConfigurator] Problem configuring service portal.wsrp:service=RegistrationManager
org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute: name=Policy value=MBeanProxyExt[portal.wsrp:service=RegistrationPolicy] on mbean portal.wsrp:service=Registr\
ationManager; - nested throwable: (java.lang.RuntimeException: Error creating MBeanProxy: portal.wsrp:service=RegistrationPolicy)

.....


Caused by: javax.management.InstanceNotFoundException: portal.wsrp:service=RegistrationPolicy is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523)
at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:666)
at org.jboss.mx.util.MBeanProxyExt.init(MBeanProxyExt.java:407)

[prabhat.jha]

The latest run has only 5 failures and all are related to wsrp. So, DB tests are 100%.

[julien1]

Less than 900 tests are executed and the error logged is

Ant Error Message: /home/cruisecontrol/work/scripts/build-jboss-portal-db.xml:41: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-portal-db.xml:97: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.

could you check that ?

[prabhat.jha]

Hi Julien,


We are comparing apple and oranges here. :-)

The regular portal 2.6 testsuite is run against three AS version while DB is running with only 4.0.4.GA but seven different DB configs..

For example: there are 7 different DB config so we have (7*14=98) tests for DB and (14*3=42) tests for regular case. All tests in regular case are run three times while in DB case only DB tests are run against multiple times. I looked into other modules and they seem to fit this logic as well. It's hard to debug if there is no bug. :-)

[prabhat.jha]

I meant that there are 14 tests in org.jboss.portal.test.cms.commands package.

[julien1]

I think it comes from the fact that for the core tests, I have added the need for remote debugging and those tests are not executed. I have fixed that.

[prabhat.jha]

Ok. I was trying to figure out which tests are not runnign as part of DB but are as par tof regular runs. Core tests were not running in both cases so it did not come in my radar.