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
i.e. testing won't run, and the Test Explorer output window shows:
Running tests (pytest): %USERPROFILE%\Code\external\pyvistaqt
Running test with arguments: --rootdir %USERPROFILE%\Code\external\pyvistaqt --override-ini junit_family=xunit1 --junit-xml=%LOCALAPPDATA%\Temp\tmp-47320qoETK7OKy2kS.xml
Current working directory: %USERPROFILE%\Code\external\pyvistaqt
Workspace directory: %USERPROFILE%\Code\external\pyvistaqt
Run completed, parsing output
Error while running tests: pyvistaqt
TypeError: Cannot read properties of null (reading 'testsuites')
Error while running tests:
TypeError: Cannot read properties of null (reading 'testsuites')
Finished running tests!
Diagnostic data
Python version (& distribution if applicable, e.g. Anaconda): 3.8.10 x64-bit (CPython)
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): venv
Value of the python.languageServer setting: Default
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Running tests (pytest): %USERPROFILE%\Code\external\pyvistaqt
Running test with arguments: --rootdir %USERPROFILE%\Code\external\pyvistaqt --override-ini junit_family=xunit1 --junit-xml=%LOCALAPPDATA%\Temp\tmp-47320qoETK7OKy2kS.xml
Current working directory: %USERPROFILE%\Code\external\pyvistaqt
Workspace directory: %USERPROFILE%\Code\external\pyvistaqt
Run completed, parsing output
Error while running tests: pyvistaqt
TypeError: Cannot read properties of null (reading 'testsuites')
Error while running tests:
TypeError: Cannot read properties of null (reading 'testsuites')
Finished running tests!
> Test run finished at 6/26/2022, 2:14:48 PM <
User Settings
languageServer: "Pylance"
linting
• flake8Enabled: true
• flake8Path: "${workspaceFolder}/.venv/Scripts/flake8.exe"
• mypyArgs: [
"--config-file",
"mypy.ini"
]
• mypyEnabled: true
• mypyPath: "${workspaceFolder}/.venv/Scripts/mypy.exe"
• pylintPath: "${workspaceFolder}/.venv/Scripts/pylint.exe"
formatting
• provider: "black"
• blackArgs:
line-length = 72
skip-string-normalization = true
target-version = ["py38"]
exclude='\.eggs|\.git|\.mypy_cache|\.tox|\.venv|_build|buck-out|build|dist|node_modules'
testing
• pytestArgs:
junit_family=legacy
filterwarnings =
error
ignore::ResourceWarning
# bogus numpy ABI warning (see numpy/#432)
ignore:.*numpy.dtype size changed.*:RuntimeWarning
ignore:.*numpy.ufunc size changed.*:RuntimeWarning
# from usage of numpy_to_vtk:
ignore:.*`np.bool` is a deprecated alias.*:DeprecationWarning
ignore:.*`np.int` is a deprecated alias.*:DeprecationWarning
ignore:.*`np.float` is a deprecated alias.*:DeprecationWarning
ignore:.*`np.object` is a deprecated alias.*:DeprecationWarning
ignore:.*`np.long` is a deprecated alias:DeprecationWarning
ignore:.*Converting `np\.character` to a dtype is deprecated.*:DeprecationWarning
addopts =
--mypy-ini-file mypy_test.ini
• pytestEnabled: true
• pytestPath: "${workspaceFolder}/.venv/Scripts/pytest.exe"
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
System Info
Item
Value
CPUs
Intel(R) Xeon(R) Gold 6248R CPU @ 3.00GHz (48 x 2993)
I discovered that the bug has not resurfaced. Instead, the behavior is due to an elusive bug within the pytest-qt library. For more details, please see the following issue:
Issue Type: Bug
Behaviour
For some reason, Issue #14107 has resurfaced.
Expected vs. Actual
Expected: Testing for python works and Output tab has better debug information.
Actual: Testing does not run and Output tab does not provide information that can be used to debug problem.
Steps to reproduce:
git clone
thepyvistaqt
repo,pip install
therequirements_*.txt
files, and do local editable installpy -m pip install -e .
pytest-mypy-plugins
and run tests (Tests run in both terminal and Test Explorer)pytest-mypy-testing
and run tests, but tests now no longer run in terminal nor Test Explorerpytest-mypy-testing
does not solve problemvenv
and dependencies does not solve problemRunning pytest in terminal simply outputs
i.e. testing won't run, and the Test Explorer output window shows:
Diagnostic data
python.languageServer
setting: DefaultOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)User Settings
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
System Info
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
Extensions (114)
(3 theme extensions excluded)
A/B Experiments
Extension version: 2022.8.0
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
System Info
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
A/B Experiments
The text was updated successfully, but these errors were encountered: