exnexu / akka-actor-locking Goto Github PK

This test shows that different processes can be executed at the same time for the same object.

    "process sequential LockAwareMessages with relatively small timeout" in {
      val nTimes = 1 to 10
      val now = nowLong()
      val msg = LockAwareMessage(1, () ⇒
        Future {
          val time1 = nowLong() - now
          Thread.sleep(100)
          val time2 = nowLong() - now
          self ! Timespan(1, time1, time2)
        }, 110.millis)

      nTimes.foreach(_ => lockActor ! msg)

      val timespans = nTimes.map(_ => expectMsgType[Timespan]).toList
      println(timespans)
      Timespan.isIntersecting(timespans) should be(false)
    }

test doesn't fail every time but if you run it repeatedly you will got an error.
Here is a sample result of failed test:
List(Timespan(1,32,136), Timespan(1,168,270), Timespan(1,169,273), Timespan(1,272,375), Timespan(1,274,379), Timespan(1,379,482), Timespan(1,380,484), Timespan(1,486,589), Timespan(1,483,587), Timespan(1,591,695))
As you can see the processes Timespan(1,168,270), Timespan(1,169,273) have Intersection

README states that:

lockActor ! LockAwareMessage(lock1, action1) // order is guaranteed
lockActor ! LockAwareMessage(lock1, action2) // runs right after action1 :-)

but I think this is depend on the order of arrival of LockAwareMessage.