Test

feat: introduce max_startup_sample in ClusterConfig #895

Job	Run time
Benchmark	2m 23s
Lint	13s
IPS	2m 41s
Main (7.2, 3.3)	1m 8s
Main (7.2, 3.3, compose.valkey.yaml)	1m 7s
NAT-ted Environments	55s
Massive Cluster	2m 46s
Main (7.2, 3.3, compose.ssl.yaml)	1m 17s
Profiling (single)	49s
Main (7.2, 3.3, hiredis)	1m 3s
Profiling (excessive_pipelining)	43s
Main (7.2, 3.3, hiredis, compose.ssl.yaml)	1m 24s
Profiling (pipelining_in_moderation)	49s
Main (7.2, 3.3, 2, compose.replica.yaml)	57s
Profiling (original_mget)	44s
Main (7.2, 3.2, compose.auth.yaml)	1m 0s
Profiling (emulated_mget)	1m 2s
Main (7.0, 3.1)	1m 13s
Main (6.2, 3.0)	1m 6s
Main (5.0, 2.7)	1m 18s
Main (jruby)	1m 56s
Main (truffleruby)	1m 31s
Main (test_cluster_state, 7.2, 2, compose.replica.yaml, 9)	5m 55s
Main (test_cluster_state, 6.2, 2, compose.replica.yaml, 9)	6m 2s
Main (test_cluster_broken, 7.2, no, 6)	2m 5s
Main (test_cluster_broken, 6.2, no, 6)	2m 15s
Main (test_cluster_scale, 7.2, compose.scale.yaml, 8)	1m 50s
Main (test_cluster_scale, 6.2, compose.scale.yaml, 8)	2m 12s
	48m 24s

Provide feedback