Test Result : EpochCoordinatorSuite

0 failures (±0)
10 tests (±0)
Took 0.12 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 k9 msPassed
several epochs, max epoch backlog reached by epochsWaitingToBeCommitted11 msPassed
several epochs, max epoch backlog reached by partitionCommits6 msPassed
several epochs, max epoch backlog reached by partitionOffsets14 msPassed
several epochs, messages arrive in order 1 -> 3 -> 4 -> 210 msPassed
several epochs, messages arrive in order 1 -> 3 -> 5 -> 4 -> 27 msPassed
single epoch60 msPassed
single epoch, all but one reader partition has reported an offset1 msPassed
single epoch, all but one writer partition has committed2 msPassed