CanonicalLtd / raft-test

78%

master: 78%

LAST BUILD ON BRANCH dont-use-command-events-for-disconnections

branch: dont-use-command-events-for-disconnections

CHANGE BRANCH

x

Reset

• dont-use-command-events-for-disconnections
• adapt-to-v1
• add-control-api
• add-find-leader
• add-hook-index
• add-latency-knob
• add-logging-to-fsm-watcher
• expose-testing-writer
• fix-control-close-hanging
• fsm-watcher
• improve-observability
• lower-default-timeouts
• master
• move-to-canonicalltd
• scenarios-v2
• support-for-deposing-immediately

Build # 128

Build Type

push

travis-ci

Committed by freeekanayaka

Commit Message

Don't use Term.When().Command() to schedule disconnections

That turned out to be problematic because leadership can be lost and re-acquired
when disconnecting and then reconnecting a follower.

Instead, there are now explicit Term.Disconnect() and Term.Reconnect() APIs that
account for leadership glitches.

Run Details

1043 of 1343 relevant lines covered (77.66%)

29.97 hits per line