Package: python3-tqdm
Version: 4.67.1-3
Severity: important
Dear Maintainer,
I'm seeing reproducible autopkgtest failures (segmentation fault) on
python3-nxtomomill. I've started debugging that using the following lines in
debian/rules:
export PYBUILD_TEST_CUSTOM=1
export PYBUILD_TEST_ARGS={interpreter} -X faulthandler -m pytest -p
no:faulthandler -v -k "not test_fluo2nx_application_"
This allowed me to get the following stacktrace of the interpreter at the
moment of the segfault:
[...]
nxtomomill/utils/tests/test_utils.py::TestChangeImageKeyControl::testUpdateToFlat
PASSED [ 98%]
nxtomomill/utils/tests/test_utils.py::TestChangeImageKeyControl::testUpdateToInvalid
PASSED [ 98%]
nxtomomill/utils/tests/test_utils.py::TestChangeImageKeyControl::testUpdateToProjections
PASSED [ 99%]
nxtomomill/utils/tests/test_utils.py::TestAddDarkAndFlatFromADifferentFolderWithVDS::test
PASSED [100%]
=============================== warnings summary
===============================
../../../../usr/lib/python3/dist-
packages/tomoscan/framereducer/framereducerbase.py:4
/usr/lib/python3/dist-packages/tomoscan/framereducer/framereducerbase.py:4:
DeprecationWarning: numpy.core.numerictypes is deprecated and has been renamed
to numpy._core.numerictypes. The numpy._core namespace contains private NumPy
internals and its use is discouraged, as NumPy internals can change without
warning in any release. In practice, most real-world usage of numpy.core is to
access functionality in the public NumPy API. If that is the case, use the
public NumPy API. If not, you are using NumPy internals. If you would still
like to access an internal attribute, use numpy._core.numerictypes.generic.
from numpy.core.numerictypes import generic as numy_generic
nxtomomill/app/tests/test_edf2nx_app.py::test_edf2nx_application
/usr/lib/python3/dist-packages/tqdm/std.py:636: TqdmWarning: clamping frac to
range [0, 1]
full_bar = Bar(frac,
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================ 168 passed, 3 deselected, 2 warnings in 29.38s
================
Fatal Python error: Segmentation fault
Current thread 0x00007f2e7675d780 (most recent call first):
Garbage-collecting
File "/usr/lib/python3/dist-packages/tqdm/std.py", line 576 in format_meter
File "/usr/lib/python3/dist-packages/tqdm/std.py", line 1151 in __str__
File "/usr/lib/python3/dist-packages/tqdm/std.py", line 1495 in display
File "/usr/lib/python3/dist-packages/tqdm/std.py", line 1302 in close
File "/usr/lib/python3/dist-packages/tqdm/std.py", line 1148 in __del__
Segmentation fault
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=139: cd
/tmp/autopkgtest.4irIce/autopkgtest_tmp/build; {interpreter} -X faulthandler -m
pytest -p no:faulthandler -v -k "not test_fluo2nx_application_"
This seems to point at tqdm, so I'm reporting this to you :-) I'm marking this
bug as important since it breaks another unrelated package.
The segfault is quite reproducible in a cowbuilder chroot during autopkgtest
runs, but for some reason it doesn't seem to happen during the test phase of
the build.
Thanks,
Roland.
[Please disregard the "system information" below, I run reportbug on a
different workstation; the bug really is about unstable]
-- System Information:
Debian Release: 12.10
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-31-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-tqdm depends on:
ii python3 3.11.2-1+b1
python3-tqdm recommends no packages.
python3-tqdm suggests no packages.
-- no debconf information
