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

Cancelling workflow does not kill parsl_utils/main.sh #7

Open
stefangary opened this issue Dec 22, 2023 · 0 comments
Open

Cancelling workflow does not kill parsl_utils/main.sh #7

stefangary opened this issue Dec 22, 2023 · 0 comments

Comments

@stefangary
Copy link
Contributor

When I start a parsl_utils workflow, if I cancel it in the GUI, parsl_utils/main.sh (and subprocesses - which includes the Parsl workflow script main.py in the workflow child processes that are launched once parsl_utils/main.sh finishes the workflow setup) is still running. For example:

sfgary@pw-user-sfgary:~/pw$ ps -u sfgary -HF
UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
sfgary    2961     1  0  1206  2060   0 14:42 ?        00:00:00 bash parsl_utils/main.sh
sfgary    3232  2961  0 405188 115464 6 14:42 ?        00:00:07   python3 -u main.py
sfgary    3291  3232  4 314783 106064 8 14:42 ?        00:00:53     python3 -u main.py
sfgary    3306  3232  4 404899 106248 6 14:42 ?        00:00:53     python3 -u main.py

What is also really unclear to me is why there are two python3 -u main.py child sub processes running - shouldn't there be only one? Perhaps there is one for each interchange that is starting up - the example above is for a two-site workflow (MDLite).

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

No branches or pull requests

1 participant