Bug#905394: spyder-kernel: Re: spyder-kernels: Please clarify why you disable the testsuite
Drew Parsons
dparsons at debian.org
Mon Jan 20 19:21:55 GMT 2020
Package: python3-spyder-kernels
Followup-For: Bug #905394
The zmq problem has now cleared. Build-time tests now proceed, but
actually pytest does not find any tests. utils/test_utils.py and other
tests have not been configured for pytest.
Hence `python3 -m pytest` returns 5 ("No tests found") and consequently
`pybuild --test` returns 13, causing the build to fail.
`python3 -m unittest` does not find tests either.
This is (attempting) testing spyder-kernel 1.8.1.
spyder-kernel's tests are not functioning.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-spyder-kernels depends on:
ii python3 3.7.5-3
ii python3-cloudpickle 1.2.1-2
ii python3-ipykernel 5.1.3-1
ii python3-jupyter-client 5.3.4-1
ii python3-zmq 17.1.2-4
python3-spyder-kernels recommends no packages.
python3-spyder-kernels suggests no packages.
-- no debconf information
More information about the debian-science-maintainers
mailing list