[jbosscache-commits] JBoss Cache SVN: r5739 - core/trunk/src/test/java/org/jboss/cache/lock/pessimistic.

[jbosscache-commits at lists.jboss.org]

Author: manik.surtani at jboss.com
Date: 2008-04-28 19:24:31 -0400 (Mon, 28 Apr 2008)
New Revision: 5739

Modified:
   core/trunk/src/test/java/org/jboss/cache/lock/pessimistic/ConcurrentPutRemoveTest.java
Log:
This test should be disabled till 3.0.0

Modified: core/trunk/src/test/java/org/jboss/cache/lock/pessimistic/ConcurrentPutRemoveTest.java
===================================================================
--- core/trunk/src/test/java/org/jboss/cache/lock/pessimistic/ConcurrentPutRemoveTest.java	2008-04-28 23:19:14 UTC (rev 5738)
+++ core/trunk/src/test/java/org/jboss/cache/lock/pessimistic/ConcurrentPutRemoveTest.java	2008-04-28 23:24:31 UTC (rev 5739)
@@ -24,7 +24,7 @@
 // The problem is in the way READ_COMMITTED is implemented, i.e., writers are not blocked by readers and this
 // allows a reader to hold a lock when a writer comes in and deletes the node in question.
 
- at Test(groups = {"functional"}, enabled = true)
+ at Test(groups = "functional", enabled = false)
 // Known issue - See JBCACHE-1164 and JBCACHE-1165
 public class ConcurrentPutRemoveTest
 {
@@ -61,7 +61,7 @@
       }
    }
 
-   @Test(invocationCount = 500, enabled = true)
+   @Test(invocationCount = 500, enabled = false)
    // TODO: 3.0.0: This is still a known failure.  MVCC in 3.0.0 will fix this; enable it in 3.0.0.
    public void testLock() throws Exception
    {