Test Result : EpochCoordinatorSuite

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

All Tests

Test nameDurationStatus
consequent epochs, a message for epoch k arrives after messages for epoch (k + 1)7 msPassed
consequent epochs, messages for epoch (k + 1) arrive after messages for epoch k11 msPassed
several epochs, max epoch backlog reached by epochsWaitingToBeCommitted25 msPassed
several epochs, max epoch backlog reached by partitionCommits15 msPassed
several epochs, max epoch backlog reached by partitionOffsets50 msPassed
several epochs, messages arrive in order 1 -> 3 -> 4 -> 211 msPassed
several epochs, messages arrive in order 1 -> 3 -> 5 -> 4 -> 212 msPassed
single epoch35 msPassed
single epoch, all but one reader partition has reported an offset2 msPassed
single epoch, all but one writer partition has committed6 msPassed