You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Clear All test Results
Run All tests - from the root test to ensure that all tests are run
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
The text was updated successfully, but these errors were encountered:
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
Does this issue occur when all extensions are disabled?: No
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.
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
The text was updated successfully, but these errors were encountered: