Test Result : EpochCoordinatorSuite

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

All Tests

Test nameDurationStatus
consequent epochs, a message for epoch k arrives after messages for epoch (k + 1)8 msPassed
consequent epochs, messages for epoch (k + 1) arrive after messages for epoch k8 msPassed
several epochs, max epoch backlog reached by epochsWaitingToBeCommitted25 msPassed
several epochs, max epoch backlog reached by partitionCommits18 msPassed
several epochs, max epoch backlog reached by partitionOffsets30 msPassed
several epochs, messages arrive in order 1 -> 3 -> 4 -> 28 msPassed
several epochs, messages arrive in order 1 -> 3 -> 5 -> 4 -> 212 msPassed
single epoch41 msPassed
single epoch, all but one reader partition has reported an offset3 msPassed
single epoch, all but one writer partition has committed3 msPassed