A comment in the test says "Use rounding to accommodate for processing delays", but in fact the test uses simple integer division instead of rounding, so if the timing of the test run is right, a 1 millisecond delay is enough to make the test fail. ~_{The processing delay doesn't matter, because the server stores the lifespan exactly as it was set by the client.}~

java.lang.AssertionError: expected:<16324694> but was:<16324693>
	at org.infinispan.server.hotrod.HotRodFunctionalTest.testLifespan2x(HotRodFunctionalTest.java:534)

Edit: The last sentence would be true for testLifespan3x, but the Hot Rod 2.x protocol allows the client to set an absolute expiration time as a number of seconds since the Unix epoch.