Closed etothepii closed 3 years ago
I'm having the same error since the last VSCode update, looks like an integration issue. My tests are executing correctly with pytest cli
Another one here with the same error.
Yep. Seeing the same thing. I downgraded to vscode 1.53 and things are working again. Same thing happens with Insdiers build too.
I did notice that the standard vscode testing tree works ok.
I spent the last 3 hours trying to figure out the same issue. Looks like if the test is in the same directory as the workspace then the test will run, all other tests will turn "blue" and then "grey", same as all reporters above. I am using 1.55 and insider with this issue. I remember last time I used 1.53 and it is working well. FYI
I have the same issue. I noticed that it works with Unittest and the problem only occurs with Pytest.
I have confirmed that regressing to v1.53.2 solves the problem, unfortunately VSCode is a little "upgrade happy" so will likely upgrade me and break again.
Sorry for the wait 😥 I can confirm the issue. Will try to fix it today.
No need to apologise! A short term work around has been identified.
Thank you for working hard @kondratyev-nv <3
I've published a new version 0.6.7. Please, update and let me know if the issue persists.
Works for me now on Win10 Pro, for both Insiders and Stable (V1.54.3).
Version: 1.54.3 (user setup)
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T10:55:45.459Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.19042
thanks, works for me as well. thanks again!
It's great to see all this green again! :)
Thanks a lot @kondratyev-nv for your great work!
I'm still having this issue in vscode 1.56.2 running in WSLv1(Ubuntu 20.04.2 LTS), with extension version 0.6.8, using pytest 5.4.3. All tests turn blue and seemingly run, but they all turn grey at the end.
Tests work correctly in python extension test module and from terminal, as in above comments.
Sorry to reopen this :(
@farfalk I think this is might be another issue. Can you please post it as a new issue and add some more details, like testing framework (maybe plugins), some output from CLI run, and whether there are any weird messages in Python Test Adapter logs.
@farfalk I think this is might be another issue. Can you please post it as a new issue and add some more details, like testing framework (maybe plugins), some output from CLI run, and whether there are any weird messages in Python Test Adapter logs.
Sorry for the extremely late response, I missed the notification. I tested it again today after more than a month, and reproduced the issue with vscode 1.58.2. BUT I SOLVED IT, doing what follows:
.pytest_cache
folder in root folder__pycache__
folder in the test folderSince this, everything works without any issue. Reproduced the fix in all my existing projects, with multiple python versions.
I have a couple of tests set up using pytest.
When I click play they go blue with the elipsis
But then return.
This appears to be happening on both my and my co-founders computers across multiple projects and appears to have started occurring sometime during last night (everything was working at 2000 GMT on Tuesday 16th March.
I can't see that a new version has been released, but as it is happening on multiple computers across multiple projects I assume something external has changed.
setting.json looks like:
The python test adapter log appears free of errors:
The tests run correctly with
pytest .
Update
Errors can be caused to appear on uncompilable code.