I cant because we have some experiments running (I didnt update before, just used another newer server)

yes, it was left by mistake (it calls)
from clearml import Taskdoesnt change the behavior

clearml version 1.0.5, Server 1.1.0
code for reproduce

` import multiprocessing

from machine_learning.clearml_client import Task

def init_clearml_task(patch_set_name, model_name, is_ensemble):
task_name = f'{patch_set_name} {model_name}'
task = Task.init(
project_name=f"bla CV",
task_name=task_name,
tags=[model_name, patch_set_name],
reuse_last_task_id=False
)
task.connect({"bla": "bla"}, 'IbexConfig')
return task

def execu...

do you say when running on 1.6.0 you see 3 tasks? (where I see 2)

try this one (even when running without debug)
` import multiprocessing
import time

from clearml import Task

def init_clearml_task(patch_set_name, model_name, is_ensemble):
task_name = f'{patch_set_name} {model_name}'
task = Task.init(
project_name=f"bla CV",
task_name=task_name,
tags=[model_name, patch_set_name],
reuse_last_task_id=False
)
task.connect({"bla": "bla"}, 'IbexConfig')
return task

def execute_1():
print("proc1")
task...

from some reason it happend in the example I gave when running in debug only, maybe matter of timing, but it happend in my "real" script also not in debugging

I updated the versions to clearml 1.6.2 Server 1.5.0, it still happening , when calling
init_clearml_task('summary', 'alg1_debug_cml', is_ensemble=False)clearml doesnt create a new task, but now the process doesn't crush

I will update to 1.6 after the weekend and check

python 3.6.9

thanks! let me know how it goes! :)