Python extension unittest discovery can't import cupy

Issue Type: Bug

Behaviour

Expected vs. Actual

Expected: Tests to be discovered correctly using unittest

Actual: ModuleNotFoundError: No module named 'cupy' in Python output on test discovery, no tests discovered.

Commenting out import cupy allows tests to be discovered with import numpy and import skimage.draw in my actual use case.

Steps to reproduce:

Create an Anaconda environment with cupy
Select env from (1) as interpreter in VSCode
Create a file src.py with import cupy
Create a file test_src.py with from src import *
Add the following to project settings.json:

"python.testing.unittestArgs": ["-v", "-s", ".", "-p", "test_*.py"],
"python.testing.pytestEnabled": false,
"python.testing.unittestEnabled": true

Test discovery should fail at this point with a ModuleNotFoundError: No module named 'cupy', including traceback.

Running test discovery at the command line works as expected using

python -m unittest discover -v -s . -p test_*.py

Commenting out import cupy allows discovery to proceed.

What's really interesting about this is I don't need any actual tests or to use import unittest to reproduce the issue.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.9.7
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Pylance

User Settings


defaultLS: {"defaultLSType":"Pylance"}

downloadLanguageServer: true

envFile: "<placeholder>"

venvPath: "<placeholder>"

venvFolders: "<placeholder>"

condaPath: "<placeholder>"

pipenvPath: "<placeholder>"

poetryPath: "<placeholder>"

languageServer: "Pylance"

linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: false
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"

sortImports
• args: "<placeholder>"
• path: "<placeholder>"

formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "black"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"

testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: false
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: true
• autoTestDiscoverOnSaveEnabled: true

terminal
• activateEnvironment: true
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"

experiments
• enabled: false
• optInto: []
• optOutFrom: []

tensorBoard
• logDirectory: "<placeholder>"

Extension version: 2022.4.0
VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2592)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.71GB (4.04GB free)
Process Argv	--folder-uri file:///d%3A/repos/uabrc.github.io --crash-reporter-id c8e5394e-cde4-4439-b1c1-1599e605633a
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
pythonvsnew555:30457759
vscscmwlcmc:30438804
vscgsvidc:30447482
cppdebug:30465021
pynewfile477:30463512

William Warriner (@wwarriner)

William Warriner (@wwarriner) Can you try doing this?

Navigate to your project from anaconda prompt
Activate the environment you want.
Then launch VS Code from the activated terminal using code .

That should work better in this scenario.

Karthik Nadig (@karthiknadig)

Hi Karthik Nadig (@karthiknadig) I appreciate the response. I tried that just now and I get the same error.

I should add that this is new behavior for an existing workspace. I have been working fine with the same workspace since at least as far back as November 2021. The last time I worked with it, before today, was about 2-3 weeks ago, and test discovery worked as expected. I made no changes since then, and it was no longer working today.

William Warriner (@wwarriner)

I believe this is the same or very similar to an issue my team are having. After updating the Python VSCode extension tests are no longer discovered in the test explorer and the error shown is ModuleNotFoundError: No module named 'dash'. We are also using Anaconda.

The tests fine running python -m unittest in the VSCode terminal.

This issue only started since updating the extension (to v2022.4.0) and downgrading the extension from v2022.4.0 to v2022.2.1924087327 solves the issue - all tests are discovered. ie changing nothing else and only swapping extension versions "fixes" and reintroduces the error.

I believe our setup is the same as described by William Warriner (@wwarriner) so just mentioning what I've managed to look at so far.

Navigating to the repo in a conda terminal and running code . to open VSCode does not solve the issue either

Thanks for the help.

Hi everyone, can you provide the following logs? Preferably for both for the extension versions: one which works and the latest version.

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output for Python test in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python test)

XXX

It lists the commands we run for test discovery.

I believe I am experiencing the same issue. On my system, since version 2022.4.0 of the extension, test discovery always fails in projects that use conda environments when any module from that environment is needed. This happens both in projects that use unittest and those that use pytest. Projects that use pytest always fail with ModuleNotFoundError: No module named 'pytest'. So it appears that test discovery is not using the project environments. Running code . from the project directory after activating the conda environment doesn't help and the resulting logs are the same (except timestamps).

This is with VS Code 1.66.0 on Windows 10.0.19044. My conda version is 4.12.0; it is provided by miniforge. It has Python 3.9.12 in its base environment, but my projects' conda environments all use Python 3.10.4. The workaround of downgrading the extension to version 2022.2.1924087327, as IsaacMulberry did, also works for me. The project for which I've included logs below is configured to use Pytest.

.vscode/settings.json

{
    "python.testing.pytestArgs": [
        "."
    ],
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true
}

Here are the logs from Python in the Output panel for both versions of the extension:

v2022.2.1924087327 (working)

Experiment 'pythonaacf' is active
Experiment 'pythonTensorboardExperiment' is active
Experiment 'PythonPyTorchProfiler' is active
Experiment 'pythonDeprecatePythonPath' is active
Experiment 'pythonInterpreterInfoPinned' is active
> conda info --json
> ~\miniforge3\envs\18845-repro\python.exe ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
> "C:\Program Files\Python310\python.exe" ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
> C:\msys64\ucrt64\bin\python.exe ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
Python interpreter path: ~\miniforge3\envs\18845-repro\python.exe
> C:\msys64\usr\bin\python.exe ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
[ERROR 2022-3-4 15:48:35.717]: [Error: Command failed: C:\msys64\usr\bin\python.exe c:\Users\ek\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py c:\Users\ek\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
/usr/bin/python: can't open file '/c/Users/ek/AppData/Local/Programs/Microsoft VS Code/c:\Users\ek\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py': [Errno 2] No such file or directory

	at ChildProcess.exithandler (node:child_process:406:12)
	at ChildProcess.emit (node:events:390:28)
	at maybeClose (node:internal/child_process:1064:16)
	at Socket.<anonymous> (node:internal/child_process:450:11)
	at Socket.emit (node:events:390:28)
	at Pipe.<anonymous> (node:net:687:12)] {
  killed: false,
  code: 2,
  signal: null,
  cmd: 'C:\\msys64\\usr\\bin\\python.exe c:\\Users\\ek\\.vscode\\extensions\\ms-python.python-2022.2.1924087327\\pythonFiles\\get_output_via_markers.py c:\\Users\\ek\\.vscode\\extensions\\ms-python.python-2022.2.1924087327\\pythonFiles\\interpreterInfo.py'
}
> ~\.conda\Scripts\conda.exe info --json
> ~\.condarc\Scripts\conda.exe info --json
> ~\miniforge3\Scripts\conda.exe info --json
> ~\miniforge3\python.exe ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
> ~\miniforge3\envs\algoviz-basics\python.exe ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
> ~/miniforge3/Scripts/activate && conda activate 18845-repro && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2022.2.1924087327/pythonFiles/printEnvVariables.py
> ~\miniforge3\envs\algoviz-basics-qa\python.exe ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\interpreterInfo.py
Starting Pylance language server.
> ~/miniforge3/Scripts/activate && conda activate 18845-repro && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2022.2.1924087327/pythonFiles/printEnvVariables.py
> ~\miniforge3\Scripts\conda.exe run -n 18845-repro --no-capture-output --live-stream python ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.2.1924087327\pythonFiles\testing_tools\run_adapter.py discover pytest -- --rootdir . -s --cache-clear .
cwd: .

v2022.4.0 (broken)

Experiment 'pythonaacf' is active
Experiment 'pythonTensorboardExperiment' is active
Experiment 'PythonPyTorchProfiler' is active
Experiment 'pythonDeprecatePythonPath' is active
Experiment 'pythonInterpreterInfoPinned' is active
> conda info --json
> ~\miniforge3\envs\18845-repro\python.exe ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
> "C:\Program Files\Python310\python.exe" ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
> C:\msys64\ucrt64\bin\python.exe ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
Python interpreter path: ~\miniforge3\envs\18845-repro\python.exe
> C:\msys64\usr\bin\python.exe ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
[ERROR 2022-3-4 15:52:0.455]: [Error: Command failed: C:\msys64\usr\bin\python.exe c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
/usr/bin/python: can't open file '/c/Users/ek/AppData/Local/Programs/Microsoft VS Code/c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py': [Errno 2] No such file or directory

	at ChildProcess.exithandler (node:child_process:406:12)
	at ChildProcess.emit (node:events:390:28)
	at maybeClose (node:internal/child_process:1064:16)
	at Socket.<anonymous> (node:internal/child_process:450:11)
	at Socket.emit (node:events:390:28)
	at Pipe.<anonymous> (node:net:687:12)] {
  killed: false,
  code: 2,
  signal: null,
  cmd: 'C:\\msys64\\usr\\bin\\python.exe c:\\Users\\ek\\.vscode\\extensions\\ms-python.python-2022.4.0\\pythonFiles\\get_output_via_markers.py c:\\Users\\ek\\.vscode\\extensions\\ms-python.python-2022.4.0\\pythonFiles\\interpreterInfo.py'
}
> conda run -n 18845-repro --no-capture-output --live-stream python ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.4.0/pythonFiles/printEnvVariables.py
> ~\miniforge3\python.exe ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
> ~\miniforge3\envs\algoviz-basics\python.exe ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
> ~\miniforge3\envs\algoviz-basics-qa\python.exe ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\interpreterInfo.py
Starting Pylance language server.
> conda run -n 18845-repro --no-capture-output --live-stream python ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.4.0/pythonFiles/printEnvVariables.py
> conda run -n 18845-repro --no-capture-output --live-stream python ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\run_adapter.py discover pytest -- --rootdir . -s --cache-clear .
cwd: .
[ERROR 2022-3-4 15:52:21.214]: Error discovering pytest tests:
 [r [Error]: Traceback (most recent call last):
  File "c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py", line 26, in <module>
    runpy.run_path(module, run_name="__main__")
  File "C:\Users\ek\miniforge3\lib\runpy.py", line 268, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "C:\Users\ek\miniforge3\lib\runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "C:\Users\ek\miniforge3\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\run_adapter.py", line 17, in <module>
    from testing_tools.adapter.__main__ import parse_args, main
  File "c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\adapter\__main__.py", line 9, in <module>
    from . import pytest, report
  File "c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\adapter\pytest\__init__.py", line 7, in <module>
    from ._discovery import discover
  File "c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\adapter\pytest\_discovery.py", line 8, in <module>
    import pytest
ModuleNotFoundError: No module named 'pytest'
ERROR conda.cli.main_run:execute(41): `conda run python c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\run_adapter.py discover pytest -- --rootdir c:\Users\ek\source\repos\18845-repro -s --cache-clear .` failed. (See above for error)

	at ChildProcess.<anonymous> (c:\Users\ek\.vscode\extensions\ms-python.python-2022.4.0\out\client\extension.js:32:38969)
	at Object.onceWrapper (node:events:510:26)
	at ChildProcess.emit (node:events:390:28)
	at maybeClose (node:internal/child_process:1064:16)
	at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)]

With both versions of the extension, all the log lines up to and including Starting Pylance language server. appear when I start VS Code (I am starting it by running code . from the project directory in PowerShell with the environment activated.)

The subsequent lines are appended to logs when I click Testing (the beaker icon) in the activity bar (which I expect, since that triggers test discovery).

I find that nothing is logged in Output > Python Test Log when test discovery fails (or otherwise before tests run), so I haven't included that. (I don't have anything exactly called Python test in the drop-down menu in the Output panel; Python Test Log is the closest.)

I hope this may be helpful. Please let me know if I should give any further information. Thanks!

Kartik Raj (@karrtikr)

Hi Kartik Raj (@karrtikr), happy to provide that info for the non-working version. This is in the context of the minimal example I started the issue with.

Python output:

> ~\AppData\Local\Continuum\anaconda3\condabin\conda.bat run -n base --no-capture-output --live-stream python ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.4.0\pythonFiles\testing_tools\unittest_discovery.py . test_*.py
cwd: .
[ERROR 2022-3-4 15:35:5.936]: Error discovering unittest tests:
 Failed to import test module: test_src
Traceback (most recent call last):
  File "C:\Users\wwarr\AppData\Local\Continuum\anaconda3\lib\unittest\loader.py", line 436, in _find_test_path
    module = self._get_module_from_name(name)
  File "C:\Users\wwarr\AppData\Local\Continuum\anaconda3\lib\unittest\loader.py", line 377, in _get_module_from_name
    __import__(name)
  File "c:\Users\wwarr\Desktop\unittest_bug\test_src.py", line 3, in <module>
    from src import *
  File "c:\Users\wwarr\Desktop\unittest_bug\src.py", line 1, in <module>
    import cupy
ModuleNotFoundError: No module named 'cupy'

There is no Python Test Log output. Presumably because no tests have been run, though I can't say for sure here.

To get info for the working version I would need to know how to roll back to an older extension version. How can I do this?

And not to derail things, maybe it is related, but I'm also seeing the issue with numpy and mkl when debugging tests that myself and others have seen in the past. Similar to the issue we're discussing, the numpy test debug issue was working three weeks ago and is not now. The text for that is below.

[C:\Users\wwarr\AppData\Local\Continuum\anaconda3\envs\eyelineate\lib\site-packages\numpy\__init__.py:148](): UserWarning: mkl-service package failed to import, therefore Intel(R) MKL initialization ensuring its correct out-of-the box operation under condition when Gnu OpenMP had already been loaded by Python process is not assured. Please install mkl-service package, see [http://github.com/IntelPython/mkl-service]()
  from . import _distributor_init

Kartik Raj (@karrtikr)

I can confirm that changing python.condaPath from C:\Users\IsaacMulberry\anaconda3\Scripts\conda-script.py to C:\Users\IsaacMulberry\anaconda3\Scripts\conda.exe does solve the issue and all tests are discovered.

Thanks Kartik Raj (@karrtikr)

I can confirm also that changing python.condaPath appropriately allows test discovery to work as expected.

Thanks everyone, https://github.com/microsoft/vscode-python/suites/5947251954/artifacts/203903588 contains a fix for the issue where everything should ideally work without setting python.condaPath. You can use Extension: Install from VSIX command to install it. Feel free to give it a try and let me know if it's still a issue.

This works for me. After deliberately bringing back the problem by clearing the value of python.condaPath in my user settings, I installed v2022.5.2099471260-dev obtained by that link, and the problem went away again (with python.condaPath still no longer specified).

Thanks!

Navigation Menu

Repository navigation

Python extension unittest discovery can't import cupy #18845

Behaviour

Expected vs. Actual

Steps to reproduce:

Diagnostic data

5 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Python extension unittest discovery can't import cupy #18845

Description

Behaviour

Expected vs. Actual

Steps to reproduce:

Diagnostic data

Activity

karthiknadig commented on Apr 1, 2022

wwarriner commented on Apr 1, 2022

IsaacMulberry commented on Apr 4, 2022

karrtikr commented on Apr 4, 2022

EliahKagan commented on Apr 4, 2022

wwarriner commented on Apr 4, 2022

5 remaining items

IsaacMulberry commented on Apr 5, 2022

wwarriner commented on Apr 5, 2022

karrtikr commented on Apr 6, 2022

EliahKagan commented on Apr 6, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions