Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

increase ticks per slot for test #3491

Merged
merged 1 commit into from
Nov 6, 2024
Merged

increase ticks per slot for test #3491

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions local-cluster/tests/local_cluster.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1546,9 +1546,16 @@ fn test_wait_for_max_stake() {
// make a root and derive the new leader schedule in time.
let stakers_slot_offset = slots_per_epoch.saturating_mul(MAX_LEADER_SCHEDULE_EPOCH_OFFSET);
// Reduce this so that we can complete the test faster by advancing through
// slots/epochs faster. But don't make it too small because it can make us
// susceptible to skipped slots and the cluster getting stuck.
let ticks_per_slot = 16;
// slots/epochs faster. But don't make it too small because it can cause the
// test to fail in two important ways:
// 1. Increase likelihood of skipped slots, which can prevent rooting and
// lead to not generating leader schedule in time and cluster getting
// stuck.
// 2. Make the cluster advance through too many epochs before all the
// validators spin up, which can lead to not properly observing gossip
// votes, not repairing missing slots, and some subset of nodes getting
// stuck.
let ticks_per_slot = 32;
let num_validators = 4;
let mut config = ClusterConfig {
cluster_lamports: DEFAULT_CLUSTER_LAMPORTS,
Expand Down
Loading