You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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).
The text was updated successfully, but these errors were encountered:
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 onceparsl_utils/main.sh
finishes the workflow setup) is still running. For example: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).The text was updated successfully, but these errors were encountered: