Fix ClusterCommand tearDown as gossip may take some time to send data to nodes

src/test/java/redis/clients/jedis/tests/commands/ClusterCommandsTest.java

@@ -9,6 +9,7 @@ import org.junit.Test;
 
 import redis.clients.jedis.HostAndPort;
 import redis.clients.jedis.Jedis;
+import redis.clients.jedis.exceptions.JedisDataException;
 import redis.clients.jedis.tests.HostAndPortUtil;
 import redis.clients.jedis.tests.JedisTestBase;
 
@@ -48,6 +49,11 @@ public class ClusterCommandsTest extends JedisTestBase {
 		node1.clusterDelSlots(5000, 10000);
 		node1.clusterDelSlots(6000);
 		node2.clusterDelSlots(6000,1,2,3,4,5,500,5000);
+		try {
+			node2.clusterDelSlots(10000);
+		} catch (JedisDataException jde) {
+			//Do nothing, slot may or may not be assigned depending on gossip
+		}
     }
 
     private static void waitForEqualClusterSize() throws InterruptedException {