raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

harden RemoteRestartedQuarantinedSpec, #17314

Browse source 
* Seems like the initial message may be dropped in this case,
  we are at-most once after all. See detailed logs in issue.
This commit is contained in:
Patrik Nordwall 2017-08-08 14:31:31 +02:00
parent 0bcf32fccb
commit 537d2c96fe
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
akka-remote-tests/src/multi-jvm/scala/akka/remote/RemoteRestartedQuarantinedSpec.scala
View file

@ -130,13 +130,13 @@ abstract class RemoteRestartedQuarantinedSpec
}
""").withFallback(system.settings.config))
// retry because it's possible to loose the initial message here, see issue #17314
val probe = TestProbe()(freshSystem)
freshSystem.actorSelection(RootActorPath(firstAddress) / "user" / "subject").tell(Identify("subject"), probe.ref)
// TODO sometimes it takes long time until the new connection is established,
// It seems like there must first be a transport failure detector timeout, that triggers
// "No response from remote. Handshake timed out or transport failure detector triggered".
probe.expectMsgType[ActorIdentity](30.second).ref should not be (None)
probe.awaitAssert({
println(s"# --") // FIXME
freshSystem.actorSelection(RootActorPath(firstAddress) / "user" / "subject").tell(Identify("subject"), probe.ref)
probe.expectMsgType[ActorIdentity](1.second).ref should not be (None)
}, 30.seconds)
// Now the other system will be able to pass, too
freshSystem.actorOf(Props[Subject], "subject")