Skip to content

Conversation

@tezc
Copy link
Collaborator

@tezc tezc commented Sep 5, 2024

#13495 introduced a change to reply -LOADING while flushing existing db on a replica.
Some of our tests are sensitive to this change and do no expect -LOADING reply.

Fixing a couple of tests that fail time to time.

@tezc tezc requested a review from sundb September 5, 2024 09:40
# Replica may start a full sync after restart, trying in a loop to avoid
# -LOADING reply in that case.
wait_for_condition 1000 50 {
[catch {set replica_dbsize_3 [R $replica_id dbsize]} e] == 0
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sundb I got a feeling that this test wants to check dbsize even before replication (just after restart). So, I added catch + loop, we'll try in a loop. Most of the time, successful execution will be before replication. On a slow CI, it might be after replication. In both cases, it should give us the correct result.

@sundb
Copy link
Collaborator

sundb commented Sep 8, 2024

seems like CI has stablized now.

@tezc tezc merged commit ac03e37 into redis:unstable Sep 8, 2024
@tezc tezc deleted the stabilize-test branch April 8, 2025 21:06
funny-dog pushed a commit to funny-dog/redis that referenced this pull request Sep 17, 2025
redis#13495 introduced a change to reply -LOADING while flushing existing db on a replica. Some of our tests are
 sensitive to this change and do no expect -LOADING reply.

Fixing a couple of tests that fail time to time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants