TESTS FAILED

Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:272: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.

Date of build: 02/13/2007 14:29:41

Time to build: 188 minutes 40 seconds

Last changed: 02/13/2007 14:10:21

Last log entry: JBAS-4079, those tests target a local JBossTM, so make it explicit

Unit Tests: (4027)  Total Errors and Failures: (23)

testWarCommonsLoggingLog4jOverrides org.jboss.test.classloader.test.ScopingUnitTestCase testTopicSelectorChange org.jboss.test.jbossmq.test.UIL2JBossMQUnitTestCase testIt org.jboss.test.jca.test.ContentiousInterleavingStressTestCase testIt org.jboss.test.jca.test.ContentiousRecyclingInterleavingStressTestCase testContentiousInterleavingStressTestcase org.jboss.test.jca.test.ContentiousRecyclingStickyStressTestCase testContentiousInterleavingStressTestcase org.jboss.test.jca.test.ContentiousStickyStressTestCase testFailoverLocalMCF org.jboss.test.jca.test.HAConnectionFactoryUnitTestCase testIt org.jboss.test.jca.test.RecyclingInterleavingStressTestCase testIt org.jboss.test.jca.test.RecyclingStickyStressTestCase testIt org.jboss.test.jca.test.RecyclingStickyWithContinuousPoisonThreadStressTestCase testIt org.jboss.test.jca.test.RecyclingStickyWithPoisonThreadStressTestCase testIt org.jboss.test.jca.test.UncontendedInterleavingStressTestCase testIt org.jboss.test.jca.test.UncontendedStickyStressTestCase testAccess org.jboss.test.jrmp.test.DynLoadingUnitTestCase testClientCertSSLAccess org.jboss.test.pooled.test.SSLSocketsUnitTestCase testTxMandatory org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase testIsNew org.jboss.test.cluster.test.CrossContextCallsTestCase(Default-UDP) testSubjectObserver org.jboss.test.cluster.test.DeprecAnnocFieldBasedTestCase(Default-TCP) testObserverRemoval org.jboss.test.cluster.test.DeprecAnnocFieldBasedTestCase(Default-TCP) testNonPrimitiveRepeatedModify org.jboss.test.cluster.test.FieldBasedTestCase(Default-TCP) testIsNew org.jboss.test.cluster.test.ScopedSetAttributeTestCase(Default-TCP) testUserTx org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase testMultipleEventDuration org.jboss.test.txtimer.test.SimpleTimerTestCase

Modifications since last build:  (first 50 of 11)
60516	modified	dimitris@jboss.org	//branches/Branch_4_2/testsuite/src/main/org/jboss/test/tm/test/AbstractTransactionLocalStressTest.java	JBAS-4079, those tests target a local JBossTM, so make it explicit
60516	modified	dimitris@jboss.org	//branches/Branch_4_2/testsuite/src/main/org/jboss/test/tm/test/TransactionLocalUnitTestCase.java	JBAS-4079, those tests target a local JBossTM, so make it explicit
60514	modified	dimitris@jboss.org	//branches/Branch_4_2/testsuite/src/main/org/jboss/test/tm/ejb/TxTimeoutBean.java	increase the timeout
60513	modified	wolfc	//branches/Branch_4_2/ejb3/build-test.xml	Creating more jars
60512	modified	wolfc	//branches/Branch_4_2/ejb3/src/test/org/jboss/ejb3/test/stateful/ServiceBean.java	Fixed ambigious injection
60512	modified	wolfc	//branches/Branch_4_2/ejb3/src/test/org/jboss/ejb3/test/stateful/StatelessBean.java	Fixed ambigious injection
60511	modified	wolfc	//branches/Branch_4_2/ejb3/src/test/org/jboss/ejb3/test/mdb/TransactionQueueTestMDB.java	Using transactionTimeout activation config property
60510	modified	wolfc	//branches/Branch_4_2/ejb3/src/test/org/jboss/ejb3/test/ejbthree751/unit/FailLocalRemoteSameInterfaceUnitTestCase.java	Fixed test
60503	modified	jfrederic.clere@jboss.com	//branches/Branch_4_2/system/src/bin/run.bat	Avoid using tools.jar because it is not needed by TC nor javassist.
60503	modified	jfrederic.clere@jboss.com	//branches/Branch_4_2/system/src/bin/run.sh	Avoid using tools.jar because it is not needed by TC nor javassist.
60501	modified	dimitris@jboss.org	//branches/Branch_4_2/testsuite/src/main/org/jboss/test/tm/test/TxTimeoutUnitTestCase.java	JBAS-4011, the arjuna transaction manager does not allow the setting of the global default tx timeout after the tx manager is started, so we won't test the default timeout setting