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

Killing a job does not actually kill it #775

Open
moi90 opened this issue Feb 15, 2022 · 0 comments
Open

Killing a job does not actually kill it #775

moi90 opened this issue Feb 15, 2022 · 0 comments
Labels

Comments

@moi90
Copy link

moi90 commented Feb 15, 2022

If I kill an export job ("Clean All (warning !!!)"), progress_msg is "Killed" (red) at first, but the job continues to run and eventually its state is "Done" (green).

If a running job can not be killed, the interface should not allow it.

This relates to #732, #674 and #149.

It seems that the following is not entirely true:

The processes just die when they try to access their task, which was deleted in DB during the user action "Clean task".

@grololo06 grololo06 self-assigned this Feb 17, 2022
@grololo06 grololo06 added the bug label Feb 17, 2022
@grololo06 grololo06 added this to the 2.6.2 milestone Feb 17, 2022
@grololo06 grololo06 modified the milestones: 2.6.2, 2.6.3 Mar 15, 2022
@grololo06 grololo06 removed their assignment Apr 20, 2022
@grololo06 grololo06 removed this from the 2.6.3 milestone May 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants