From e5159eb764d98ee9f221a29b9609db36621ce8dc Mon Sep 17 00:00:00 2001
From: Patrik Nordwall <patrik.nordwall@gmail.com>
Date: Wed, 9 Sep 2015 14:36:03 +0200
Subject: [PATCH] =cls #18176 Harden ClusterShardingLeavingSpec

In logs it is clear that the fourth node is moved to Up,
but it takes more than 5 sec to disseminate that info
---
 .../akka/cluster/sharding/ClusterShardingLeavingSpec.scala      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingLeavingSpec.scala b/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingLeavingSpec.scala
index f236cce3cc..31b79f8dfe 100644
--- a/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingLeavingSpec.scala
+++ b/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingLeavingSpec.scala
@@ -125,7 +125,7 @@ abstract class ClusterShardingLeavingSpec(config: ClusterShardingLeavingSpecConf
     runOn(from) {
       cluster join node(to).address
       startSharding()
-      within(5.seconds) {
+      within(15.seconds) {
         awaitAssert(cluster.state.members.exists { m ⇒
           m.uniqueAddress == cluster.selfUniqueAddress && m.status == MemberStatus.Up
         } should be(true))