Python testing discovery hang forever with v2025.*

[maichongju]

I have some testing set up with pytest. For some reason the test discovery just hang forever with this waning message in the output.

[warning] The cwd resolves to a different path, checking if it has a symbolic link somewhere in its path.

However, if I downgrade the version back to v2024.*. Then the test discovery will execute without issue.

We are using conda with python 3.12.9

Anyone can help me to resolve this issue?

Attached is the settings.json

{
  "python-envs.defaultEnvManager": "ms-python.python:conda",
  "python-envs.defaultPackageManager": "ms-python.python:conda",
  "python-envs.pythonProjects": [],
  "python.testing.pytestArgs": [
    "."
  ],
  "python.testing.unittestEnabled": false,
  "python.testing.pytestEnabled": true,
  "python.testing.cwd": "${workspaceFolder}/tests",
}

[eleanorjboyd]

What that step does is checks recursively if any parent directories of the given path are symbolic links. Are you using symlinks? Are you using a remote scenario or another way that might make the resolved path of the cwd (which would be "python.testing.cwd": "${workspaceFolder}/tests" for you) different from the given path?

[maichongju]

I do not use symlinks in my project. The project is run on Windows Local machine. Is there any way to troubleshoot this issue. Because the test discovery works on 2024.* just not any of the 2025.*

[eleanorjboyd]

can you try specifying the absolute path to your test folder instead of using this variable here: "python.testing.cwd": "${workspaceFolder}/tests" and see if that impacts it? If that doesn't do anything can you try with a python other than 3.12? We have seen a few issues with that version compatibility with the extension

[maichongju]

Thanks for the suggestion. I've tried both suggestions you mention in my project and none of them work. When I set the absolute path, to the cwd, the warning did goes away but no test discovery. I also tried with python 3.13, which produce the same result. I've even tried the new 2025.4.0, same behaviour.