Skip to content

Python test runner reliability issues with vs code version 1.6 #17308

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

Closed
briansmi opened this issue Sep 5, 2021 · 2 comments · Fixed by #17313
Closed

Python test runner reliability issues with vs code version 1.6 #17308

briansmi opened this issue Sep 5, 2021 · 2 comments · Fixed by #17313
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@briansmi
Copy link

briansmi commented Sep 5, 2021

Does this issue occur when all extensions are disabled?: No

  • VS Code Version:1.60.0
  • OS Version: Win 10.0.19043

Steps to Reproduce:

I just upgraded to 1.6 and I'm have serious test runner reliability issues. I'm using the ms extensions for Python and vscode-pylance. For testing I'm using python.testing.unittest. Every time I start a test run on a fraction of my ~180 tests actually run. I've never had this issue previously and my 180 test suite runs very reliably in about 10 seconds. This is really frustrating as testing is so critical to my development workflow.

  1. Clear All test Results
  2. Run All tests - from the root test to ensure that all tests are run
  3. Random number of tests (for example, 47/47 or 58/58 or 122/122) will run out of a suite of 180 tests
    4.Maybe 1 out of 8 runs will run all 180 tests

Not sure if this is related, but I see an 'ERROR: read ECONNRESET' after each test execution in the python output

@wind-chh
Copy link

wind-chh commented Sep 7, 2021

I have the same issue. "run tests" will run a subset of all tests, and it's much more slower then ever before.

@briansmi
Copy link
Author

briansmi commented Sep 7, 2021

Looks like lots of folks are seeing this class of behavior with the new 1.6 update (or the updated ms-python extension) Here's another bug report I that I saw in the vscode-python repo: #17282

@connor4312 connor4312 assigned karthiknadig and unassigned connor4312 Sep 7, 2021
@karthiknadig karthiknadig transferred this issue from microsoft/vscode Sep 7, 2021
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 7, 2021
@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug and removed triage-needed Needs assignment to the proper sub-team labels Sep 8, 2021
@karthiknadig karthiknadig added this to the August Recovery milestone Sep 8, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants