-
Notifications
You must be signed in to change notification settings - Fork 990
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.
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
fix: Fix test_flushall_in_full_sync
#3929
Conversation
This test failed in CI many times. The issue was that we reach stable sync too quickly, and miss the full sync stage. I changed the seeder to add 100k (instead of 30k) keys for the stage to take longer.
@chakaz did you reproduce locally? |
yes, in release builds it fails locally for me >90% of times, with the fix it passed 1,000 times without failing |
tests/dragonfly/replication_test.py
Outdated
@@ -1107,7 +1107,7 @@ async def test_flushall_in_full_sync(df_factory): | |||
c_replica = replica.client() | |||
|
|||
# Fill master with test data | |||
seeder = SeederV2(key_target=30_000) | |||
seeder = SeederV2(key_target=100_000) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please use StaticSeeder or debug populate command
wow it did not fail for me :( |
maybe your machine is too slow 😆 |
Probably, is really old 😄 |
Fixes #3897 |
This test failed in CI many times. The issue was that we reach stable sync too quickly, and miss the full sync stage.
I changed the seeder to add 100k (instead of 30k) keys for the stage to take longer.