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

Python: FAILED test_async_client.py::TestScripts::test_script_kill_route #2617

Open
ikolomi opened this issue Nov 6, 2024 · 6 comments
Open
Assignees
Labels
bug Something isn't working Flaky-tests Flaky-tests python Python wrapper
Milestone

Comments

@ikolomi ikolomi added bug Something isn't working python Python wrapper Release blocker Can't release without. Flaky-tests Flaky-tests labels Nov 6, 2024
@ikolomi ikolomi added this to the 1.2 milestone Nov 6, 2024
@ikolomi ikolomi changed the title Python: FAILED test_async_client.py::TestScripts::test_script_kill_route[ProtocolVersion.RESP2-False-True] Python: FAILED test_async_client.py::TestScripts::test_script_kill_route Nov 6, 2024
@shohamazon
Copy link
Collaborator

Script kill command info:

2)  1) "script|kill"
           2) (integer) 2
           3) 1) noscript
              2) allow_busy
           4) (integer) 0
           5) (integer) 0
           6) (integer) 0
           7) 1) @slow
              2) @scripting
           8) 1) "request_policy:all_shards"
              2) "response_policy:one_succeeded"

since the response policy is one_succeeded, we might not kill the script from all running nodes (when we run with all nodes route) but we do kill from some.
So for example, we have 3 shards, 2 returned an OK response, one didnt, the whole command returned OK but we still have a running script in progress.

@acarbonetto
Copy link
Collaborator

@shohamazon would it work to direct all work to one specific shard?

@shohamazon
Copy link
Collaborator

@shohamazon would it work to direct all work to one specific shard?

You mean having a single route? Because we already have a test with a single route and looks like it works fine

@shohamazon
Copy link
Collaborator

@note : disabled for now for green CI, when fixed, need to be added back #2631

@acarbonetto
Copy link
Collaborator

@shohamazon we should add a TODO to fix this later.
We can do the same disabling for Node and Java.

@shohamazon
Copy link
Collaborator

@shohamazon we should add a TODO to fix this later.

We can do the same disabling for Node and Java.

@acarbonetto I believe this whole issue is a TODO

@ikolomi ikolomi removed the Release blocker Can't release without. label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Flaky-tests Flaky-tests python Python wrapper
Projects
Status: Backlog
Development

No branches or pull requests

3 participants