Can you please check if passing the path to the python interpreter explicitly solves the problem for you? I.e. please try (depending on the location of the python binary):
nv-nsight-cu-cli -o profile --target-processes all /usr/bin/python ./test.py
In addition, it would be helpful if you could let us know your operating system and the output of
Thank you. This is very likely a known issue related to tracking processes spawned via execv(). We will provide a fix for this in an upcoming release. In the meantime, as a workaround, you can try to launch your script with a python 2 interpreter, which sometimes behaves differently in terms of process management.