RE: [jbosscache-dev] More breaking UTs in HEAD

OK, looks like there is a problem in the Cache passivation failure that causes PojoCache passivation to fail as well. But it should go away when you have them in order. BTW, how do things look like on your side now for the Alpha release? PojoCache is mostly ready except state transfer code and some clean up on examples and tutorial. I expect to finish them within 2-3 days. Thanks, -Ben -----Original Message----- From: jbosscache-dev-bounces(a)lists.jboss.org [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani Sent: Saturday, September 16, 2006 8:02 PM To: jbosscache-dev(a)lists.jboss.org Subject: [jbosscache-dev] More breaking UTs in HEAD Hi guys The reason for a higher failure rate in CC is that I added a whole bunch of unit tests to stress the new move() API in various ways. Some of these need fixing (such as deep locks on nodes when moving subtrees and optimistic locks on subtrees, notifications while moving, and cacheloader/passivation code to reflect moves) but I expect these to be in place Monday. Just in case you were wondering why the test pass-rate dropped from 98.5% to 92.5%! :-) Cheers, -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat Email: manik(a)jboss.org Telephone: +44 7786 702 706 MSN: manik(a)surtani.org Yahoo/AIM/Skype: maniksurtani _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev