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
Tried the other applicable steps from the Troubleshooting Guide
Completed the Problem Description, Steps to Reproduce and Version sections below
Problem Description
Oh, I'm sorry, there were more failures that I hadn't realised, as they aborted rather than reporting a failure. :-( And there's a new failure with spyder 5.2.1.
Anyway, here's the first one: the tests in spyder/plugins/workingdirectory/tests/ almost all segfault when run outside of the context of the whole runtests.py suite. Here's an example.
What steps reproduce the problem?
euler:~/debian/spyder-packages/spyder/build-area/spyder-5.2.1+dfsg1 $ python3.9 -m pytest spyder/plugins/workingdirectory/tests/test_workingdirectory.py::test_basic_initialization
============================= test session starts ==============================
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
PyQt5 5.15.6 -- Qt runtime 5.15.2 -- Qt compiled 5.15.2
rootdir: /home/jdg/debian/spyder-packages/spyder/build-area/spyder-5.2.1+dfsg1, configfile: pytest.ini
plugins: typeguard-2.11.1, lazy-fixture-0.6.3, hypothesis-5.43.3, order-1.0.0, anyio-3.4.0, xvfb-2.0.0, mock-3.6.1, xdist-2.4.0, timeout-2.0.1, cov-3.0.0, forked-1.3.0, qt-4.0.2, dependency-0.5.1, flaky-3.7.0
collected 1 item
spyder/plugins/workingdirectory/tests/test_workingdirectory.py Fatal Python error: Aborted
Current thread 0x00007f1a1fb5a740 (most recent call first):
File "/home/jdg/debian/spyder-packages/spyder/build-area/spyder-5.2.1+dfsg1/spyder/api/widgets/main_container.py", line 106 in __init__
File "/home/jdg/debian/spyder-packages/spyder/build-area/spyder-5.2.1+dfsg1/spyder/api/plugins/new_api.py", line 313 in __init__
File "/home/jdg/debian/spyder-packages/spyder/build-area/spyder-5.2.1+dfsg1/spyder/plugins/workingdirectory/tests/test_workingdirectory.py", line 37 in setup_workingdirectory
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 932 in call_fixture_func
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 1126 in pytest_fixture_setup
File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in <lambda>
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 1072 in execute
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 687 in _compute_fixture_value
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 601 in _get_active_fixturedef
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 581 in getfixturevalue
File "/usr/lib/python3/dist-packages/_pytest/fixtures.py", line 568 in _fillfixtures
File "/usr/lib/python3/dist-packages/pytest_lazyfixture.py", line 39 in fill
File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1647 in setup
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 449 in prepare
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 150 in pytest_runtest_setup
File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in <lambda>
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 255 in <lambda>
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 311 in from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 254 in call_runtest_hook
File "/usr/lib/python3/dist-packages/flaky/flaky_pytest_plugin.py", line 138 in call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 120 in runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 109 in pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/flaky/flaky_pytest_plugin.py", line 94 in pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in <lambda>
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 348 in pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in <lambda>
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 323 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 269 in wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 316 in pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in <lambda>
File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 162 in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 185 in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in <module>
File "/usr/lib/python3.9/runpy.py", line 87 in _run_code
File "/usr/lib/python3.9/runpy.py", line 197 in _run_module_as_main
Aborted
This happens in a regular desktop session and using xvfb-run in a chroot. I'm a bit stymied on this one, I'm afraid. Aborting tests seem challenging to debug.
But when I run runtests.py on the whole test suite, it claims that all of the tests in test_workingdirectory.py pass. So it might be some sort of initialisation problem, perhaps, as with #17074.
What is the expected output? What do you see instead?
I expect the test to pass, not abort.
Versions
Spyder version: 5.2.1
Python version: 3.9 and 3.10
Qt version: 5.15.2
PyQt version: 5.15.6+dfsg-1+b1
Operating System name/version: Debian testing and unstable
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
Oh, I'm sorry, there were more failures that I hadn't realised, as they aborted rather than reporting a failure. :-( And there's a new failure with spyder 5.2.1.
Anyway, here's the first one: the tests in
spyder/plugins/workingdirectory/tests/
almost all segfault when run outside of the context of the wholeruntests.py
suite. Here's an example.What steps reproduce the problem?
This happens in a regular desktop session and using
xvfb-run
in a chroot. I'm a bit stymied on this one, I'm afraid. Aborting tests seem challenging to debug.But when I run
runtests.py
on the whole test suite, it claims that all of the tests intest_workingdirectory.py
pass. So it might be some sort of initialisation problem, perhaps, as with #17074.What is the expected output? What do you see instead?
I expect the test to pass, not abort.
Versions
Dependencies
The text was updated successfully, but these errors were encountered: