Test Result : EpochCoordinatorSuite

0 failures (±0)
10 tests (±0)
Took 0.14 sec.

All Tests

Test nameDurationStatus
consequent epochs, a message for epoch k arrives after messages for epoch (k + 1)5 msPassed
consequent epochs, messages for epoch (k + 1) arrive after messages for epoch k6 msPassed
several epochs, max epoch backlog reached by epochsWaitingToBeCommitted14 msPassed
several epochs, max epoch backlog reached by partitionCommits11 msPassed
several epochs, max epoch backlog reached by partitionOffsets20 msPassed
several epochs, messages arrive in order 1 -> 3 -> 4 -> 25 msPassed
several epochs, messages arrive in order 1 -> 3 -> 5 -> 4 -> 29 msPassed
single epoch70 msPassed
single epoch, all but one reader partition has reported an offset1 msPassed
single epoch, all but one writer partition has committed3 msPassed