Code lens not showing up for nose, running a single test method executes it twice

1. No configuration changes occured during this.
2. Code lens for testing started acting up (like here or here ), i.e. started “lagging” behind changes and being misplaced.
3. After restart, tests were no longer found by the extension, and stopped showing up in code at all. Note that F1 > “Run All Unit Tests” still ran nosetests with proper configuration, and output to the test console. See “actual behavior” below.

Relevant part of setup.cfg:

[nosetests]
verbosity=0
with-doctest=0
with-coverage=1
cover-package=RedactedPackageName

Environment data

• VS Code version: 1.26.1
• Extension version (available under the Extensions sidebar): 2018.7.1
• OS and version: Windows 10 pro
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.6.6, Conda 4.5.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda env
• Relevant/affected Python packages and their versions: nose=1.3.7=py36_2 coverage=4.5.1=py36hfa6e2cd_0
• Linter: flake8

Have Git Lens installed, but line features are disabled.

Actual behavior

Tests run just fine, but extension doesn’t notice. (This is the “Python Tests” panel)

Expected behavior

Tests are found, code lens shows “Run Test | Debug Test” buttons again.

Steps to reproduce:

No idea, sorry. I tried getting it working, obviously, but I can’t reproduce it on my home machine.

Logs

Python console log:

Starting Jedi Python language engine.
##########Linting Output - flake8##########

For Python Testing, see the screenshot above (“Actual Behavior”).

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help):

[spiu]

I found out that codelens issue is related to the gitlens extension probably deleting other’s. When disabled I see the run/debug test codelenses show up correctly.

Moving from nose to pytest removes the tests from running twice

[brettcannon]

I get the code lenses, but the double execution is still occurring.