2009/10/23 Rajith Attapattu <[email protected]> > I have temporarily excluded the following tests from the cpp test > profiles to get them green. > All these tests have been added within the last 2 weeks. > I will investigate them one by one to ensure if any of the failures > are genuine or needs to be permanently disabled. > > Are these tests run against the 0-10 Java Broker? > If so I'd be interested to know the outcome. > > org.apache.qpid.test.unit.publish.DirtyTrasactedPubilshTest > org.apache.qpid.test.unit.ack.FailoverBeforeConsumingRecoverTest > org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverTest > org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverOnMessageTest > > org.apache.qpid.test.client.RollbackOrderTest#testOrderingAfterRollbackOnMessage > > > Running the tests against the Java 0-10 broker, I get failures on AcknowledgeAfterFailoverOnMessageTest (testTransacted,testNoAck ans testPreAck when I ran it)... abd AcknowledgeAfterFailoverTest<file:///home/rob/java-broker-0-10/qpid/java/build/report/org/apache/qpid/test/unit/ack/180_AcknowledgeAfterFailoverTest.html>(testPreAck) ... even on the InVM (0-8) tests I was getting race conditions on these - I've fixed one case (where there was a deadlock because we weren't checking if a connection was in the process of closing before starting a send and taking the Failover lock)... but there seemed to be some other intances where it would deadlock on connection close with Failover. AFAICT nothing in this area had been changed by my 0-10 work... so I'm going to assume that those race conditions are in trunk also...
-- Rob > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
