-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Error running test with pytest #4334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Btw., running python 3.6.7.
|
Seems like I get the following when I use the command "run all unit tests".
|
I just ran into the same or a similar issue. Running the tests again via the tests button in the bottom status bar seems to (at least temporarily) have solved the problem. |
I'm getting the same error despite passing tests:
Bug keeps appearing and disappearing. Log:
|
I'm getting this issue too. It also seems to stop the inline error highlighting updating. VSCode: 1.47.1 Python Test Log Output:
I only get this if running tests using vscode. Using cli works fine. |
We are going through old issues and we noticed that no one from the team had replied to this issue. I want to apologize for the oversight and to let you know that the issue was reviewed by the team and triaged (as shown by the labels applied to this issue). |
is this issue related to #12403 by any chance? |
@Almenon I believe they are different issues. |
Still experiencing in vscode:
python 3.8 Fixed by Re-Discovering the tests |
Same issue :
I believe it was caused by a test previously discovered, then commented and that was trying to be run through "Run all tests" button. |
I'm getting this now I think, and no matter what I do I can't get it working. In VS code I configure "Cwd" as "src", since that's where the source code for my Django project is. root dir contains all the config files, docker stuff etc. With "src" in place, test explorer shows the tests, but they can't run. Without it, nothing is found. If I run the tests with "src" set as cwd, I get an error telling me it couldn't find I've removed At the moment, I'm resorting to running my tests manually outside of VS Code. Any news on this issue? |
Just encountered the same issue. Simple test passes from Terminal, but fails with this error in VSCode. Running "Rediscover all tests" fixes it. |
I ran into the same error. The path it was searching for was wrong. |
Hello! I have reviewed this issue and given the architectural changes of the testing rewrite, this issue should no longer exist on the rewrite. Therefore I am going to close this issue but please comment or open a new issue if you are still seeing a problem when you try this yourself! To use the rewrite yourself just add Thanks! |
Issue Type: Bug
I have a simple test scenario which yields some errors in vs code. I'm trying to run the following little program with the Python extension:
I get the following two errors:
This path seems to be wrong, given that the path to the program is
/home/erikah/ok/plattform/python_testing/test
Extension version: 2019.1.0
VS Code version: Code 1.31.0 (7c66f58312b48ed8ca4e387ebd9ffe9605332caa, 2019-02-06T08:51:24.856Z)
OS version: Linux x64 4.15.0-45-generic
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
surface_synchronization: enabled_on
video_decode: unavailable_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: