'Released lock' messages occur every time `release()` succeeds. This causes this message to occur with very large `seconds` (say 12434454234.0 seconds) since `self._lock_acquired_seconds` is 0. See https://github.com/rackerlabs/silverberg/pull/33/files#L0R165. Here, `self._reactor.seconds()` will return seconds since EPOCH (I think). While testing using `clock`, `clock.seconds()` returns 0 until it is advanced. So, to simulate real conditions I advance it before passing it.