Skip to content

Conversation

@karajan1001
Copy link
Contributor

fix: #7587

  1. Add implement kill method for local queue class
  2. Add a test to make sure the following job will be success after the
    original job was killed.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

@karajan1001 karajan1001 requested a review from pmrowla May 9, 2022 10:24
@karajan1001 karajan1001 requested a review from a team as a code owner May 9, 2022 10:24
test_queue.kill("bar")

while True:
if result_foo.status == "SUCCESS":
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Here, even if we killed the process "bar", the result_bar.status still returns "SUCCESS", only celery.control.revoke would make it fail, and this is why the following "foo" process will continue.

@pmrowla
Copy link
Contributor

pmrowla commented May 13, 2022

Looks good, just squash or cleanup your commits to get rid of the "review fix" type messages and we can merge this

fix: treeverse#7587
1. Add implement kill method for local queue class
2. Add a test to make sure the following job will be success after the
   original job was killed.
3. Some refactoring work on `exp remove`
@pmrowla pmrowla merged commit 35d7921 into treeverse:dvc-task-dev May 14, 2022
@karajan1001 karajan1001 deleted the fix7587 branch May 18, 2022 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A: experiments Related to dvc exp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants