Testing always raises "Unable to read file" #10658
Comments
sralloza
added
triage-needed
ghost
removed
the
|
Hi @sralloza, thank you for reaching out! I extracted your comment about the JUnit warning in a different issue (#10673), thank you for reporting it 👍 Does this error get raised when you run a single failing test, when you run all tests, or both? What does your folder structure look like? Do you have a What happens if you run
Thanks! |
|
Here you have the requested info:
Both.
I don't have a
If I run the tests using pytest directly in terminal, the output is what you would expect, without any For some reason, now I can't reproduce my own bug. I created a test designed to fail, just like I did when I submitted this issue, and it just works fine. Now, executing the test I may add that this bug was present in other projects, too. I think it may be related with the mock library, because in one occasion when I commented a hole test that was using mock badly, the bug disappeared. But the moment I uncommented that test, the bug returned. It's something that may be useful, although I can't 100% confirm this. |
|
Good news, I finally found a way to reproduce the bug. As I recalled, it is caused by a misuse of the Steps to reproduce:Create a project with this structure: Contents of file class A:
b = 25
def substract(b):
return A.b - bContents of file from src.mod import substract
from unittest import mock
@mock.patch("invalid_route.mod.A.b", 100)
def test_substract():
assert substract(2) == 98Contents of file from distutils.core import setup
setup(name="src")Notes:
After installing But, running the tests with vscode-python will return the mentioned |
|
Thank you for investigating the issue and providing a sample repro case! Seems like there's an issue with how we parse pytest's output 🔍 |
kimadeline
added
needs PR
area-testing
and removed
info-needed
|
I have the same problem, looking forward to a fix. |
|
I think it has to do with a module importing issue. I was trying to resolve a circular relative import issue and encountered this. |
|
Is there a fix for this yet? I think one was proposed here: This just makes it difficult to work. Thanks! |
|
Experiencing this today, not a fun one! |
|
I think this was closed in #16769. Feel free to comment if you are still experiencing this issue. |
Environment data
"python.jediEnabled"set to; more info How to update the language server to the latest stable version #3977): jedipython.languageServersetting: MicrosoftExpected behaviour
Launching a test should not raise any
Unable to read fileerror.Actual behaviour
When launching a test (pytest is enabled as testing framework) and it fails, an error is raised:
Error: Error: cannot open file:///d%3A/.scripts/vcm/c. Detail: Unable to read file 'd:\.scripts\vcm\c' (Error: Unable to resolve non-existing file 'd:\.scripts\vcm\c').The route of the workspace is
d:\.scripts\vcm, but there is no file namedc. If I create a file namedc, the error changes toError: Error: Illegal value for 'line'.If at first all tests are ok, no error is raised. But when the first tests fail, then after every test (even if it doesn't fail) the error of the
cfile appears again.The
Unable to read fileerror was mentioned in #6548, and theIllegal value for lineerror was mentioned in #4334.I have tried to disable all extensions except for vscode-python, but the bug is still there.
Also, running tests with pytests shows the
PytestDeprecationWarning: The 'junit_family' default value will change to 'xunit2' in pytest 6.0. Add 'junit_family=xunit1' to your pytest.ini file to keep the current format in future versions of pytest and silence this warning.Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
I tried to create a blank project with a similar structure as mine, but I can't recreate the bug
Logs
Output for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)Output of
Python Test Log:Output from `Console` under the `Developer Tools` panel (toggle Developer Tools on under `Help`; turn on source maps to make any tracebacks be useful by running `Enable source map support for extension debugging`)
To provide more information, these are my settings:
Global settings:
Workspace settings:
The text was updated successfully, but these errors were encountered: