Repository navigation
Test discovery doesn't work into container #21637
Description
Activity
Thank you for your issue report. We are looking into this now! In the meantime, you are likely on the new testing rewrite and this is why you saw a change in behavior since we just moved to this experiment to a larger group of people receiving it. You can opt out of the rewrite as I get this fix in by setting this in your user settings:
"python.experiments.optOutFrom": ["pythonTestAdapter"],. If this doesn't work let me know as this will mean it is a different issue. Thank you and I will send updates in this thread as I get a fix in.Eleanor Boyd (@eleanorjboyd)
unfortunately, this also does not work for me, tried following settings:"python.experiments.optInto": [ "pythonTestAdapter" ], "python.experiments.enabled": false,without any visual success
If I am using just
"python.experiments.optInto": [ "pythonTestAdapter" ]nothing changed, issue is the same
I am using 2023.8.0 extension version as a temporary solution. 2023.12.0 not 2023.10.1 does not work for me
Yevhen Dmytrenko (@akarev0) just to confirm did you try to set this setting in your user settings not your workspace settings? Seeing a few people presenting similar errors and opting out of the experiment was a solution for them. Just trying to determine if these issues are the same or different. Thanks for your help and quick replies!
Eleanor Boyd (@eleanorjboyd) yes, I am sure that I am using user settings, but I just understood that they doesn't make any sense because I am using devcontainer which is remote workspace and those settings doesn't work. They are inactive according to color schema
partially impacted by pytest-dev/pytest#11235, but will also look at what else is breaking since I think there are multiple issues
- added a commit that references this issue
on Jul 28, 2023 recently released python
2023.14.0doesn't fix anything(Eleanor Boyd (@eleanorjboyd) I don't know if it matters but I am using some custom things like:
pytest_pluginsinto highest level likeTests/conftest.pyto load some fixtures- at the same file I am also using
pytest_addoptionit looks like
def pytest_addoption(parser): parser.addoption("--replay_test_dir", action="store") parser.addoption("--replay_test_manifest", action="store")- also I am using addopts into my
pytest.ini
Hope that it will help you guys to figure out where is the bug
Hi! We had to roll back this fix due to a bug so the fix is not out in the most recent release. Hopefully we will get it out soon and then you can test it from there. Thanks!
FYI - also seeing this when using remote SSH.
v2023.14.0
Oliver Mannion (@tekumara) are you seeing this on insiders? The fix is out there but not on stable.
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!
- locked as resolved and limited conversation to collaborators
on Oct 22, 2023
Hi there, I used devcontainer for my work but I cannot now, I can discover the tests, but I cannot run it because of incorrect path (as I can assume because debug setup with full path from launch.json works fine)
I am using following setting for my devcontainer:
but as I can see while I am trying to run test path starts from one folder inside and not tests folder, for example:
unit/test_third_api.pywhile it should be:
Tests/unit/test_third_api.pybecause path is incorrect I see
Error: ERROR: file or directory not found: integration/...Since I am using devcontainer top level folder was
apppreviously, not it is one level into it notappbutTestsAlso color indication does not work at all I mean it does not representing any info, not green check marks nor red crosses
OS: ubuntu 22.04
vscode: 1.80.0
Temporary solution: change extension version from 2023.12.0 to 2023.8.0 works fine for me