Repository navigation
Tests not discovered, but running tests anyway works fine. #16593
Description
Discussed in #16565
Originally posted by bigjools June 25, 2021
I've got a very simple unittest-based set up. My settings.json has this:
"python.testing.unittestEnabled": true,
"python.testing.unittestArgs": [
"-s",
"sofi.tests"
],
When doing test discovery I get this output:
Test Discovery failed:
Error: spawn /path/to/my/python3 ENOENT
However I can run the tests just fine! I get the output in the Python Debug console.
/usr/bin/env /path/to/my/python3 /my/homedir/.vscode/extensions/ms-python.python-2021.6.944021595/pythonFiles/lib/python/debugpy/launcher 45627 -- /my/homedir/.vscode/extensions/ms-python.python-2021.6.944021595/pythonFiles/visualstudio_py_testlauncher.py --us=sofi.tests --up=test*.py --uvInt=1 --result-port=34281
.........................................................s.....................
----------------------------------------------------------------------
Ran 79 tests in 0.311s
Can anyone shed any light on this?
(Running 1.57.1 on Ubuntu 20.04, Python extension version 2021.6.944021595)
Activity
bigjools commentedon Jul 1, 2021
#16594
kimadeline commentedon Jul 5, 2021
Hi Julian Edwards (@bigjools),
Thank you for reaching out and for your PR. Before we take a look at it, would you mind sharing your unittest setup, and the content of the
Pythonoutput channel?Thanks!
bigjools commentedon Jul 5, 2021
It's best to look at the Discussion I used to raise this issue, and the PR I submitted at #16594 (where I also asked for a bit of help as I have no experience with Typescript).
luabud commentedon Sep 2, 2021
I believe this has been fixed hence closing it 😊