Your message dated Fri, 15 Dec 2023 14:08:46 +0000
with message-id <zxxd7p2vpt9pe...@d-and-j.net>
and subject line Re: Bug#1058402: spyder-kernels: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
has caused the Debian Bug report #1058402,
regarding spyder-kernels: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1058402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-kernels
Version: 2.5.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>    dh_update_autotools_config -O--buildsystem=pybuild
>    dh_autoreconf -O--buildsystem=pybuild
>    dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>    dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/_version.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/py3compat.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spyderpdb.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/utils.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/namespace_manager.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/umr.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spydercustomize.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/customize
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/dochelpers.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/mpl.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/test_utils.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/iofuncs.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/nsview.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/misc.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/lazymodules.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/utils
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/kernel.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/shell.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/outstream.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__main__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/start.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/console
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/commbase.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/frontendcomm.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/spyder_kernels/comms
> running egg_info
> creating spyder_kernels.egg-info
> writing spyder_kernels.egg-info/PKG-INFO
> writing dependency_links to spyder_kernels.egg-info/dependency_links.txt
> writing requirements to spyder_kernels.egg-info/requires.txt
> writing top-level names to spyder_kernels.egg-info/top_level.txt
> writing manifest file 'spyder_kernels.egg-info/SOURCES.txt'
> reading manifest file 'spyder_kernels.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE.txt'
> adding license file 'AUTHORS.txt'
> writing manifest file 'spyder_kernels.egg-info/SOURCES.txt'
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/_version.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> copying spyder_kernels/py3compat.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spyderpdb.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/utils.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/namespace_manager.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/umr.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> copying spyder_kernels/customize/spydercustomize.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/customize
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/dochelpers.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/mpl.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/test_utils.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/iofuncs.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/nsview.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/misc.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> copying spyder_kernels/utils/lazymodules.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/utils
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/kernel.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/shell.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/outstream.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/__main__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> copying spyder_kernels/console/start.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/console
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/commbase.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/comms
> copying spyder_kernels/comms/frontendcomm.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/spyder_kernels/comms
> running egg_info
> writing spyder_kernels.egg-info/PKG-INFO
> writing dependency_links to spyder_kernels.egg-info/dependency_links.txt
> writing requirements to spyder_kernels.egg-info/requires.txt
> writing top-level names to spyder_kernels.egg-info/top_level.txt
> reading manifest file 'spyder_kernels.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE.txt'
> adding license file 'AUTHORS.txt'
> writing manifest file 'spyder_kernels.egg-info/SOURCES.txt'
>    dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build; python3.12 -m 
> pytest -k "not test_dask_multiprocessing"
> ============================= test session starts 
> ==============================
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<<PKGBUILDDIR>>
> plugins: flaky-3.7.0
> collected 98 items / 1 deselected / 97 selected
> 
> console/tests/test_console_kernel.py ....................s............ss [ 
> 36%]
> ss...                                                                    [ 
> 41%]
> customize/tests/test_umr.py FFFFF                                        [ 
> 46%]
> customize/tests/test_utils.py .                                          [ 
> 47%]
> utils/tests/test_dochelpers.py .......................                   [ 
> 71%]
> utils/tests/test_iofuncs.py ...........                                  [ 
> 82%]
> utils/tests/test_lazymodules.py ..                                       [ 
> 84%]
> utils/tests/test_nsview.py ...............                               
> [100%]
> 
> =================================== FAILURES 
> ===================================
> _____________________________ test_umr_skip_cython 
> _____________________________
> 
> user_module = <function user_module.<locals>.create_module at 0x7fb5f42d0a40>
> 
>     def test_umr_skip_cython(user_module):
>         """
>         Test that the UMR doesn't try to reload modules when Cython
>         support is active.
>         """
>         # Create user module
>         user_module('foo')
>     
>         # Activate Cython support
>         os.environ['SPY_RUN_CYTHON'] = 'True'
>     
>         # Create UMR
> >       umr = UserModuleReloader()
> 
> customize/tests/test_umr.py:55: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> spyder_kernels/customize/umr.py:61: in __init__
>     self.activate_cython()
> spyder_kernels/customize/umr.py:107: in activate_cython
>     import pyximport
> /usr/lib/python3/dist-packages/pyximport/__init__.py:1: in <module>
>     from .pyximport import *
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
>     """
>     Import hooks; when installed with the install() function, these hooks
>     allow importing .pyx files as if they were Python modules.
>     
>     If you want the hook installed every time you run Python
>     you can add it to your Python version by adding these lines to
>     sitecustomize.py (which you can create from scratch in site-packages
>     if it doesn't exist there or somewhere else on your python path)::
>     
>         import pyximport
>         pyximport.install()
>     
>     For instance on the Mac with a non-system Python 2.3, you could create
>     sitecustomize.py with only those two lines at
>     /usr/local/lib/python2.3/site-packages/sitecustomize.py .
>     
>     A custom distutils.core.Extension instance and setup() args
>     (Distribution) for for the build can be defined by a <modulename>.pyxbld
>     file like:
>     
>     # examplemod.pyxbld
>     def make_ext(modname, pyxfilename):
>         from distutils.extension import Extension
>         return Extension(name = modname,
>                          sources=[pyxfilename, 'hello.c'],
>                          include_dirs=['/myinclude'] )
>     def make_setup_args():
>         return dict(script_args=["--compiler=mingw32"])
>     
>     Extra dependencies can be defined by a <modulename>.pyxdep .
>     See README.
>     
>     Since Cython 0.11, the :mod:`pyximport` module also has experimental
>     compilation support for normal Python modules.  This allows you to
>     automatically run Cython on every .pyx and .py module that Python
>     imports, including parts of the standard library and installed
>     packages.  Cython will still fail to compile a lot of Python modules,
>     in which case the import mechanism will fall back to loading the
>     Python source modules instead.  The .py import mechanism is installed
>     like this::
>     
>         pyximport.install(pyimport = True)
>     
>     Running this module as a top-level script will run a test and then print
>     the documentation.
>     
>     This code is based on the Py2.3+ import protocol as described in PEP 302.
>     """
>     
>     import glob
> >   import imp
> E   ModuleNotFoundError: No module named 'imp'
> 
> /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: ModuleNotFoundError
> _________________________________ test_umr_run 
> _________________________________
> 
> user_module = <function user_module.<locals>.create_module at 0x7fb5efdbcb80>
> 
>     def test_umr_run(user_module):
>         """Test that UMR's run method is working correctly."""
>         # Create user module
>         user_module('foo1')
>     
>         # Activate verbose mode in the UMR
>         os.environ['SPY_UMR_VERBOSE'] = 'True'
>     
>         # Create UMR
> >       umr = UserModuleReloader()
> 
> customize/tests/test_umr.py:73: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> spyder_kernels/customize/umr.py:61: in __init__
>     self.activate_cython()
> spyder_kernels/customize/umr.py:107: in activate_cython
>     import pyximport
> /usr/lib/python3/dist-packages/pyximport/__init__.py:1: in <module>
>     from .pyximport import *
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
>     """
>     Import hooks; when installed with the install() function, these hooks
>     allow importing .pyx files as if they were Python modules.
>     
>     If you want the hook installed every time you run Python
>     you can add it to your Python version by adding these lines to
>     sitecustomize.py (which you can create from scratch in site-packages
>     if it doesn't exist there or somewhere else on your python path)::
>     
>         import pyximport
>         pyximport.install()
>     
>     For instance on the Mac with a non-system Python 2.3, you could create
>     sitecustomize.py with only those two lines at
>     /usr/local/lib/python2.3/site-packages/sitecustomize.py .
>     
>     A custom distutils.core.Extension instance and setup() args
>     (Distribution) for for the build can be defined by a <modulename>.pyxbld
>     file like:
>     
>     # examplemod.pyxbld
>     def make_ext(modname, pyxfilename):
>         from distutils.extension import Extension
>         return Extension(name = modname,
>                          sources=[pyxfilename, 'hello.c'],
>                          include_dirs=['/myinclude'] )
>     def make_setup_args():
>         return dict(script_args=["--compiler=mingw32"])
>     
>     Extra dependencies can be defined by a <modulename>.pyxdep .
>     See README.
>     
>     Since Cython 0.11, the :mod:`pyximport` module also has experimental
>     compilation support for normal Python modules.  This allows you to
>     automatically run Cython on every .pyx and .py module that Python
>     imports, including parts of the standard library and installed
>     packages.  Cython will still fail to compile a lot of Python modules,
>     in which case the import mechanism will fall back to loading the
>     Python source modules instead.  The .py import mechanism is installed
>     like this::
>     
>         pyximport.install(pyimport = True)
>     
>     Running this module as a top-level script will run a test and then print
>     the documentation.
>     
>     This code is based on the Py2.3+ import protocol as described in PEP 302.
>     """
>     
>     import glob
> >   import imp
> E   ModuleNotFoundError: No module named 'imp'
> 
> /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: ModuleNotFoundError
> __________________________ test_umr_previous_modules 
> ___________________________
> 
> user_module = <function user_module.<locals>.create_module at 0x7fb5efdbd260>
> 
>     def test_umr_previous_modules(user_module):
>         """Test that UMR's previos_modules is working as expected."""
>         # Create user module
>         user_module('foo2')
>     
>         # Create UMR
> >       umr = UserModuleReloader()
> 
> customize/tests/test_umr.py:86: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> spyder_kernels/customize/umr.py:61: in __init__
>     self.activate_cython()
> spyder_kernels/customize/umr.py:107: in activate_cython
>     import pyximport
> /usr/lib/python3/dist-packages/pyximport/__init__.py:1: in <module>
>     from .pyximport import *
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
>     """
>     Import hooks; when installed with the install() function, these hooks
>     allow importing .pyx files as if they were Python modules.
>     
>     If you want the hook installed every time you run Python
>     you can add it to your Python version by adding these lines to
>     sitecustomize.py (which you can create from scratch in site-packages
>     if it doesn't exist there or somewhere else on your python path)::
>     
>         import pyximport
>         pyximport.install()
>     
>     For instance on the Mac with a non-system Python 2.3, you could create
>     sitecustomize.py with only those two lines at
>     /usr/local/lib/python2.3/site-packages/sitecustomize.py .
>     
>     A custom distutils.core.Extension instance and setup() args
>     (Distribution) for for the build can be defined by a <modulename>.pyxbld
>     file like:
>     
>     # examplemod.pyxbld
>     def make_ext(modname, pyxfilename):
>         from distutils.extension import Extension
>         return Extension(name = modname,
>                          sources=[pyxfilename, 'hello.c'],
>                          include_dirs=['/myinclude'] )
>     def make_setup_args():
>         return dict(script_args=["--compiler=mingw32"])
>     
>     Extra dependencies can be defined by a <modulename>.pyxdep .
>     See README.
>     
>     Since Cython 0.11, the :mod:`pyximport` module also has experimental
>     compilation support for normal Python modules.  This allows you to
>     automatically run Cython on every .pyx and .py module that Python
>     imports, including parts of the standard library and installed
>     packages.  Cython will still fail to compile a lot of Python modules,
>     in which case the import mechanism will fall back to loading the
>     Python source modules instead.  The .py import mechanism is installed
>     like this::
>     
>         pyximport.install(pyimport = True)
>     
>     Running this module as a top-level script will run a test and then print
>     the documentation.
>     
>     This code is based on the Py2.3+ import protocol as described in PEP 302.
>     """
>     
>     import glob
> >   import imp
> E   ModuleNotFoundError: No module named 'imp'
> 
> /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: ModuleNotFoundError
> ______________________________ test_umr_namelist 
> _______________________________
> 
>     def test_umr_namelist():
>         """Test that the UMR skips modules according to its name."""
> >       umr = UserModuleReloader()
> 
> customize/tests/test_umr.py:95: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> spyder_kernels/customize/umr.py:61: in __init__
>     self.activate_cython()
> spyder_kernels/customize/umr.py:107: in activate_cython
>     import pyximport
> /usr/lib/python3/dist-packages/pyximport/__init__.py:1: in <module>
>     from .pyximport import *
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
>     """
>     Import hooks; when installed with the install() function, these hooks
>     allow importing .pyx files as if they were Python modules.
>     
>     If you want the hook installed every time you run Python
>     you can add it to your Python version by adding these lines to
>     sitecustomize.py (which you can create from scratch in site-packages
>     if it doesn't exist there or somewhere else on your python path)::
>     
>         import pyximport
>         pyximport.install()
>     
>     For instance on the Mac with a non-system Python 2.3, you could create
>     sitecustomize.py with only those two lines at
>     /usr/local/lib/python2.3/site-packages/sitecustomize.py .
>     
>     A custom distutils.core.Extension instance and setup() args
>     (Distribution) for for the build can be defined by a <modulename>.pyxbld
>     file like:
>     
>     # examplemod.pyxbld
>     def make_ext(modname, pyxfilename):
>         from distutils.extension import Extension
>         return Extension(name = modname,
>                          sources=[pyxfilename, 'hello.c'],
>                          include_dirs=['/myinclude'] )
>     def make_setup_args():
>         return dict(script_args=["--compiler=mingw32"])
>     
>     Extra dependencies can be defined by a <modulename>.pyxdep .
>     See README.
>     
>     Since Cython 0.11, the :mod:`pyximport` module also has experimental
>     compilation support for normal Python modules.  This allows you to
>     automatically run Cython on every .pyx and .py module that Python
>     imports, including parts of the standard library and installed
>     packages.  Cython will still fail to compile a lot of Python modules,
>     in which case the import mechanism will fall back to loading the
>     Python source modules instead.  The .py import mechanism is installed
>     like this::
>     
>         pyximport.install(pyimport = True)
>     
>     Running this module as a top-level script will run a test and then print
>     the documentation.
>     
>     This code is based on the Py2.3+ import protocol as described in PEP 302.
>     """
>     
>     import glob
> >   import imp
> E   ModuleNotFoundError: No module named 'imp'
> 
> /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: ModuleNotFoundError
> ___________________________ test_umr_reload_modules 
> ____________________________
> 
> user_module = <function user_module.<locals>.create_module at 0x7fb5efdbe020>
> 
>     def test_umr_reload_modules(user_module):
>         """Test that the UMR only tries to reload user modules."""
>         # Create user module
>         user_module('foo3')
>     
>         # Create UMR
> >       umr = UserModuleReloader()
> 
> customize/tests/test_umr.py:109: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> spyder_kernels/customize/umr.py:61: in __init__
>     self.activate_cython()
> spyder_kernels/customize/umr.py:107: in activate_cython
>     import pyximport
> /usr/lib/python3/dist-packages/pyximport/__init__.py:1: in <module>
>     from .pyximport import *
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
>     """
>     Import hooks; when installed with the install() function, these hooks
>     allow importing .pyx files as if they were Python modules.
>     
>     If you want the hook installed every time you run Python
>     you can add it to your Python version by adding these lines to
>     sitecustomize.py (which you can create from scratch in site-packages
>     if it doesn't exist there or somewhere else on your python path)::
>     
>         import pyximport
>         pyximport.install()
>     
>     For instance on the Mac with a non-system Python 2.3, you could create
>     sitecustomize.py with only those two lines at
>     /usr/local/lib/python2.3/site-packages/sitecustomize.py .
>     
>     A custom distutils.core.Extension instance and setup() args
>     (Distribution) for for the build can be defined by a <modulename>.pyxbld
>     file like:
>     
>     # examplemod.pyxbld
>     def make_ext(modname, pyxfilename):
>         from distutils.extension import Extension
>         return Extension(name = modname,
>                          sources=[pyxfilename, 'hello.c'],
>                          include_dirs=['/myinclude'] )
>     def make_setup_args():
>         return dict(script_args=["--compiler=mingw32"])
>     
>     Extra dependencies can be defined by a <modulename>.pyxdep .
>     See README.
>     
>     Since Cython 0.11, the :mod:`pyximport` module also has experimental
>     compilation support for normal Python modules.  This allows you to
>     automatically run Cython on every .pyx and .py module that Python
>     imports, including parts of the standard library and installed
>     packages.  Cython will still fail to compile a lot of Python modules,
>     in which case the import mechanism will fall back to loading the
>     Python source modules instead.  The .py import mechanism is installed
>     like this::
>     
>         pyximport.install(pyimport = True)
>     
>     Running this module as a top-level script will run a test and then print
>     the documentation.
>     
>     This code is based on the Py2.3+ import protocol as described in PEP 302.
>     """
>     
>     import glob
> >   import imp
> E   ModuleNotFoundError: No module named 'imp'
> 
> /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: ModuleNotFoundError
> =============================== warnings summary 
> ===============================
> ../../../../../../usr/lib/python3/dist-packages/dateutil/tz/tz.py:37
>   /usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: DeprecationWarning: 
> datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal 
> in a future version. Use timezone-aware objects to represent datetimes in 
> UTC: datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
>     EPOCH = datetime.datetime.utcfromtimestamp(0)
> 
> ../../../../../../usr/lib/python3/dist-packages/jupyter_client/connect.py:27
>   /usr/lib/python3/dist-packages/jupyter_client/connect.py:27: 
> DeprecationWarning: Jupyter is migrating its paths to use standard 
> platformdirs
>   given by the platformdirs library.  To remove this warning and
>   see the appropriate new directories, set the environment variable
>   `JUPYTER_PLATFORM_DIRS=1` and then run `jupyter --paths`.
>   The use of platformdirs will be the default in `jupyter_core` v6
>     from jupyter_core.paths import jupyter_data_dir
> 
> .pybuild/cpython3_3.12_spyder-kernels/build/console/tests/test_console_kernel.py:
>  70 warnings
>   /usr/lib/python3/dist-packages/jupyter_client/session.py:203: 
> DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled 
> for removal in a future version. Use timezone-aware objects to represent 
> datetimes in UTC: datetime.datetime.now(datetime.UTC).
>     return datetime.utcnow().replace(tzinfo=utc)
> 
> .pybuild/cpython3_3.12_spyder-kernels/build/console/tests/test_console_kernel.py::test_magics
>   /usr/lib/python3/dist-packages/IPython/core/history.py:570: 
> DeprecationWarning: The default datetime adapter is deprecated as of Python 
> 3.12; see the sqlite3 documentation for suggested replacement recipes
>     cur = conn.execute(
> 
> .pybuild/cpython3_3.12_spyder-kernels/build/console/tests/test_console_kernel.py::test_load_data
> .pybuild/cpython3_3.12_spyder-kernels/build/console/tests/test_console_kernel.py::test_save_namespace
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_iofuncs.py::test_spydata_import[export_data.spydata]
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_iofuncs.py::test_spydata_import[export_data_renamed.spydata]
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_iofuncs.py::test_spydata_import_witherror
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_iofuncs.py::test_spydata_export[spydata_values-spydata_values-export_data_copy]
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_iofuncs.py::test_spydata_export[namespace_objects_full-namespace_objects_filtered-export_data_2]
>   /usr/lib/python3.12/tarfile.py:2220: DeprecationWarning: Python 3.14 will, 
> by default, filter extracted tar archives and reject files or modify their 
> metadata. Use the filter argument to control this behavior.
>     warnings.warn(
> 
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_nsview.py::test_get_type_string
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_nsview.py:345:
>  PendingDeprecationWarning: the matrix subclass is not the recommended way to 
> represent matrices or deal with linear algebra (see 
> https://docs.scipy.org/doc/numpy/user/numpy-for-matlab-users.html). Please 
> adjust your code to use regular ndarray.
>     matrix = np.matrix([[1, 2], [3, 4]])
> 
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_nsview.py::test_is_editable_type
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_nsview.py:400:
>  PendingDeprecationWarning: the matrix subclass is not the recommended way to 
> represent matrices or deal with linear algebra (see 
> https://docs.scipy.org/doc/numpy/user/numpy-for-matlab-users.html). Please 
> adjust your code to use regular ndarray.
>     matrix = np.matrix([[1, 2], [3, 4]])
> 
> .pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_nsview.py::test_get_numpy_type
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build/utils/tests/test_nsview.py:438:
>  PendingDeprecationWarning: the matrix subclass is not the recommended way to 
> represent matrices or deal with linear algebra (see 
> https://docs.scipy.org/doc/numpy/user/numpy-for-matlab-users.html). Please 
> adjust your code to use regular ndarray.
>     matrix = np.matrix([[1, 2], [3, 4]])
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> ===Flaky Test Report===
> 
> test_cwd_in_sys_path passed 1 out of the required 1 times. Success!
> test_multiprocessing passed 1 out of the required 1 times. Success!
> test_multiprocessing_2 passed 1 out of the required 1 times. Success!
> test_runfile passed 1 out of the required 1 times. Success!
> test_np_threshold passed 1 out of the required 1 times. Success!
> test_matplotlib_inline passed 1 out of the required 1 times. Success!
> test_debug_namespace passed 1 out of the required 1 times. Success!
> 
> ===End Flaky Test Report===
> =========================== short test summary info 
> ============================
> FAILED customize/tests/test_umr.py::test_umr_skip_cython - 
> ModuleNotFoundErro...
> FAILED customize/tests/test_umr.py::test_umr_run - ModuleNotFoundError: No 
> mo...
> FAILED customize/tests/test_umr.py::test_umr_previous_modules - 
> ModuleNotFoun...
> FAILED customize/tests/test_umr.py::test_umr_namelist - ModuleNotFoundError: 
> ...
> FAILED customize/tests/test_umr.py::test_umr_reload_modules - 
> ModuleNotFoundE...
> ===== 5 failed, 87 passed, 5 skipped, 1 deselected, 83 warnings in 42.70s 
> ======
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_spyder-kernels/build; python3.12 -m 
> pytest -k "not test_dask_multiprocessing"
> I: pybuild base:310: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build; python3.11 -m 
> pytest -k "not test_dask_multiprocessing"
> ============================= test session starts 
> ==============================
> platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<<PKGBUILDDIR>>
> plugins: flaky-3.7.0
> collected 98 items / 1 deselected / 97 selected
> 
> console/tests/test_console_kernel.py ....................s............ss [ 
> 36%]
> ss...                                                                    [ 
> 41%]
> customize/tests/test_umr.py .....                                        [ 
> 46%]
> customize/tests/test_utils.py .                                          [ 
> 47%]
> utils/tests/test_dochelpers.py .......................                   [ 
> 71%]
> utils/tests/test_iofuncs.py ...........                                  [ 
> 82%]
> utils/tests/test_lazymodules.py ..                                       [ 
> 84%]
> utils/tests/test_nsview.py ...............                               
> [100%]
> 
> =============================== warnings summary 
> ===============================
> ../../../../../../usr/lib/python3/dist-packages/jupyter_client/connect.py:27
>   /usr/lib/python3/dist-packages/jupyter_client/connect.py:27: 
> DeprecationWarning: Jupyter is migrating its paths to use standard 
> platformdirs
>   given by the platformdirs library.  To remove this warning and
>   see the appropriate new directories, set the environment variable
>   `JUPYTER_PLATFORM_DIRS=1` and then run `jupyter --paths`.
>   The use of platformdirs will be the default in `jupyter_core` v6
>     from jupyter_core.paths import jupyter_data_dir
> 
> .pybuild/cpython3_3.11_spyder-kernels/build/customize/tests/test_umr.py::test_umr_skip_cython
>   /usr/lib/python3/dist-packages/pyximport/pyximport.py:51: 
> DeprecationWarning: the imp module is deprecated in favour of importlib and 
> slated for removal in Python 3.12; see the module's documentation for 
> alternative uses
>     import imp
> 
> .pybuild/cpython3_3.11_spyder-kernels/build/utils/tests/test_nsview.py::test_get_type_string
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/utils/tests/test_nsview.py:345:
>  PendingDeprecationWarning: the matrix subclass is not the recommended way to 
> represent matrices or deal with linear algebra (see 
> https://docs.scipy.org/doc/numpy/user/numpy-for-matlab-users.html). Please 
> adjust your code to use regular ndarray.
>     matrix = np.matrix([[1, 2], [3, 4]])
> 
> .pybuild/cpython3_3.11_spyder-kernels/build/utils/tests/test_nsview.py::test_is_editable_type
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/utils/tests/test_nsview.py:400:
>  PendingDeprecationWarning: the matrix subclass is not the recommended way to 
> represent matrices or deal with linear algebra (see 
> https://docs.scipy.org/doc/numpy/user/numpy-for-matlab-users.html). Please 
> adjust your code to use regular ndarray.
>     matrix = np.matrix([[1, 2], [3, 4]])
> 
> .pybuild/cpython3_3.11_spyder-kernels/build/utils/tests/test_nsview.py::test_get_numpy_type
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_spyder-kernels/build/utils/tests/test_nsview.py:438:
>  PendingDeprecationWarning: the matrix subclass is not the recommended way to 
> represent matrices or deal with linear algebra (see 
> https://docs.scipy.org/doc/numpy/user/numpy-for-matlab-users.html). Please 
> adjust your code to use regular ndarray.
>     matrix = np.matrix([[1, 2], [3, 4]])
> 
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> ===Flaky Test Report===
> 
> test_cwd_in_sys_path passed 1 out of the required 1 times. Success!
> test_multiprocessing passed 1 out of the required 1 times. Success!
> test_multiprocessing_2 passed 1 out of the required 1 times. Success!
> test_runfile passed 1 out of the required 1 times. Success!
> test_np_threshold passed 1 out of the required 1 times. Success!
> test_matplotlib_inline passed 1 out of the required 1 times. Success!
> test_debug_namespace passed 1 out of the required 1 times. Success!
> 
> ===End Flaky Test Report===
> =========== 92 passed, 5 skipped, 1 deselected, 5 warnings in 40.76s 
> ===========
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
> 3.11" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/spyder-kernels_2.5.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Version: 2.5.0-2

On Tue, Dec 12, 2023 at 09:22:26AM +0100, Lucas Nussbaum wrote:
> Source: spyder-kernels
> Version: 2.5.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231212 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

The latest update (just uploaded) fixes this issue; I hadn't noticed
this report when I was fixing it.

Best wishes,

   Julian

--- End Message ---

Reply via email to