Hello during the build of vitables, the reunit test fail with a segfault.

platform linux -- Python 3.13.2, pytest-8.3.5, pluggy-1.5.0
rootdir: /<<PKGBUILDDIR>>
configfile: pyproject.toml
plugins: typeguard-4.4.2, xvfb-3.0.0
collected 72 items

tests/test_calculator.py . [ 1%] tests/test_filenode.py ...... [ 9%] tests/test_logger.py ..... [ 16%] tests/test_samples.py . [ 18%] tests/test_start.py ....F........... [ 40%] tests/test_utils.py ............Fatal Python error: Segmentation fault

Current thread 0x00007f16c01c2780 (most recent call first):
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 142 in runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 113 in pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 103 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 120 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 513 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 362 in pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 103 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 120 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 513 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 337 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 283 in wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 330 in pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 103 in _multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 120 in _hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 513 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 201 in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 9 in <module>
File "<frozen runpy>", line 88 in _run_code
File "<frozen runpy>", line 198 in _run_module_as_main

Extension modules: numpy._core._multiarray_umath, numpy.linalg._umath_linalg, tables._comp_lzo, tables._comp_bzip2, tables.utilsextension, numexpr.interpreter, tables.hdf5extension, tables.linkextension, tables.lrucacheextension, tables.tableextension,
tables.indexesextension, PyQt6.QtCore, PyQt6.QtGui, PyQt6.QtWidgets, PyQt6.QtOpenGL, PyQt6.QtOpenGLWidgets, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox,
numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, charset_normalizer.md (total: 26)
Segmentation fault
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=139: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build; python3.13 -m pytest tests

do we have a tool which could automatically generate a backtrace in sbuild if this kind of failure occur ?


Cheers

Fred

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Fred,

* PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> [2025-03-12 11:12]:

Hello during the build of vitables, the reunit test fail with a segfault.

[..]

Extension modules: numpy._core._multiarray_umath, numpy.linalg._umath_linalg, tables._comp_lzo, tables._comp_bzip2, tables.utilsextension, numexpr.interpreter, tables.hdf5extension, tables.linkextension, tables.lrucacheextension, tables.tableextension,

tables.indexesextension, PyQt6.QtCore, PyQt6.QtGui, PyQt6.QtWidgets, PyQt6.QtOpenGL, PyQt6.QtOpenGLWidgets, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox,
numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, charset_normalizer.md (total: 26)

Segmentation fault
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=139: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build; python3.13 -m pytest tests

do we have a tool which could automatically generate a backtrace in sbuild if this kind of failure occur ?

I am not aware of any automatism for that but you can do it manually:

$ gbp clone vcsgit:vitables
$ cd vitables
$ gbp buildpackage --git-builder=sbuild --chroot-mode=unshare --no-clean-source --anything-failed-commands %s
# inside the chroot
# apt install gdb
# cd /build/reproducible-path/vitables-3.1.0/.pybuild/cpython3_3.13/build
# export DEBUGINFOD_URLS=https://debuginfod.debian.net
# gdb --args python3.13 -m pytest tests
(gdb) bt

Cheers Jochen

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmfRZ6cACgkQW//cwljm lDNysg/+I1+v7TiaebWD9/macsSEUPhSBbvJErebMVxDyoMel9aLgq8FuHPnIVuI U1q3msr4BB59hJBgZS4O1URP9UZ70bRL61r1IdKWj28Y2tUbewIlMMiovSznIu+T o7aKs9N40aanJJ5KhEK2AgEAWiWNySRTieJi/4w5axWDRKHI4Unh5osrLMkiPHHj 46BlKujZGMmhjM18AV/WscziSfmRxmus/ETwh14XF2ch0RrNuBG4lbrjmLI3remP LyPJJ2TEOdQRh2UQ6bOEuW1mHwXSJTxCbzBKIrfWQ38wj2aTVAbsrJmZ9xdzVhpe aAF58PgviWkYgAa3meiGMbZevqmUanyb6iILGTxMPKGKVxTySAPTvm3j3HYktX6K mWXEO+2TbA8/t1672afO7GMUAOGtoQrQ05dQchHW9pqlwHQ39gxcqQ/NlhlpqJYx cNwJbzGfF6BcKGGDkgJrp/1nB2OtIlb7haS1yH6sPPqXkFC27eCn1eFllcAmup3d V90ZvD89USqk7CsWQPM95mYAUY2UGUbeoPcMpMsgdSKrewPfLk3kmBM9EApKzVdF 0gOXU9IuOc35ykwxVRIKpcauNMO0sCaSALqJ/2nATHiB1SStMoZdWRbheVq+MbEp TunA8G8BMd9SLjDLa+cSZ5M7KM45zz8dZeZ1UW8CiY73BtXXM6I=
=UdL+
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

$ gbp clone vcsgit:vitables
$ cd vitables
$ gbp buildpackage --git-builder=sbuild --chroot-mode=unshare --no-clean-source
--anything-failed-commands %s
# inside the chroot
# apt install gdb
# cd /build/reproducible-path/vitables-3.1.0/.pybuild/cpython3_3.13/build
# export DEBUGINFOD_URLS=https://debuginfod.debian.net
# gdb --args python3.13 -m pytest tests
(gdb) bt

Cheers Jochen

I am using the schroot mode where there is not network, so gdb can not download the debug info.
Is it possible to activate the network from the chroot or should the network be activated before starting the build ?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

* PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> [2025-03-12 12:31]:

$ gbp clone vcsgit:vitables
$ cd vitables
$ gbp buildpackage --git-builder=sbuild --chroot-mode=unshare --no-clean-source
--anything-failed-commands %s
# inside the chroot
# apt install gdb
# cd /build/reproducible-path/vitables-3.1.0/.pybuild/cpython3_3.13/build
# export DEBUGINFOD_URLS=https://debuginfod.debian.net
# gdb --args python3.13 -m pytest tests
(gdb) bt

Cheers Jochen

I am using the schroot mode where there is not network, so gdb can not download the debug info.
Is it possible to activate the network from the chroot or should the network be activated before starting the build ?

I am not aware of official documentation how to use schroot without
network so I don't know how you did that. Instead I would recommend to
switch to the unshare backend as that one runs dpkg-buildpackage without network but you get network in the debug shell.
And as a reminder, the buildds use sbuild+unshare for testing and
unstable.

Cheers Jochen

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmfReb4ACgkQW//cwljm lDMrPhAAplxczH12wKCPvQHFGr4WyCkBU1ybrKoHhWiLqXBawWLmElgXq3sZlQRt Ie/32gMjzY9bGWRFyy9dqPnhuK7NHAvBsHE0qdAhOvPxEY3eU7gddUoWetFygykF 4Wau5vH2YwqtVCKYA5ISHU9XbpTVRlqsUz5lXLzfC54KMDNlwR9fGrhPzGFxeSdl HaINyW45U3x3lb5TINE37bex1aARkusP+z9Bt4ALxcDFXH52coJgbkqGcAuqo9Hk /E1X0pIPPc85PylgNug5qzgnSBkwhacp+abepRVA3mmZDkHz1OeKO0WIn4I39my/ wyWIIFC/LU8P4yIDkDiFPHkoZ19eCWSKvveix1nuDIg6yLmC7IU20maOoPp5wZEj So/n3gEFhCGjAsLOBTFyDeyWWzJPvr4w/V2HgKJiAYYDWSHFExy40QOBu+yuegXV ZZb7GBg2uGP209pg1viVzQbXD+0+dH101V/3SNzJi0oksEUlvo1OVwgsdckkxpzV z7mkiTdxHecZdq0CW4erSlJRaLuI9qksqfMssoLXjk7kS/UvXGEXqs9NfqpYbQfS 1/ogOJb9FaUpVpp9L0m1UQqQUsThy68LXajDD17S1b8jeCgH0RjLZwZXZBnDW7ts qXEtUPsGcZgVSXfs7j2mABzpy8clHsvpBLlZhC4BIwet0MER2O8=
=Zrc/
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)