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.

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: test_noreply_pipeline flakiness #4102

Merged
merged 1 commit into from
Nov 10, 2024
Merged

fix: test_noreply_pipeline flakiness #4102

merged 1 commit into from
Nov 10, 2024

Conversation

romange
Copy link
Collaborator

@romange romange commented Nov 10, 2024

Fixes #3896. Now we retry several times.
In my checks this should significantly reduce the failure probability.

Fixes #3896. Now we retry several times.
In my checks this should significantly reduce the failure probability.

Signed-off-by: Roman Gershman <[email protected]>
@romange romange requested a review from kostasrim November 10, 2024 09:27
info = await client.info()
if info["total_pipelined_commands"] == 0:
logging.error("No pipelined commands were detected. Info: \n" + str(info))
for attempts in range(2):
Copy link
Contributor

Choose a reason for hiding this comment

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

https://github.com/dragonflydb/dragonfly/actions/runs/11741693909/job/32710883520#step:6:753

Second run had total_pipelined_commands=1794 so I guess the range(2) is a good number 😄

@romange romange merged commit 1eef773 into main Nov 10, 2024
12 checks passed
@romange romange deleted the FixMC branch November 10, 2024 11:39
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.

pymemcached_test.py::test_noreply_pipeline fails
2 participants