Your message dated Wed, 01 Jul 2026 12:22:04 +0000
with message-id <[email protected]>
and subject line Bug#1140692: fixed in python-memray 1.19.3+dfsg-2
has caused the Debian Bug report #1140692,
regarding python-memray: FTBFS on armhf (segfault)
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 [email protected]
immediately.)


-- 
1140692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140692
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-memray
Version: 1.19.3+dfsg-1
Severity: serious
X-Debbugs-CC: [email protected]

[copied to Colin as the most recent uploader]

Hi,

python-memray FTBFS on armhf with a segfault. This has occurred on both
arm-conova-01 and arm-ubc-02.

Relevant-looking log extract:

tests/integration/test_object_tracking.py::test_object_tracking_in_threads 
PASSED [ 10%]
tests/integration/test_object_tracking.py::test_object_stack_trace_with_native_traces
 Fatal Python error: Segmentation fault

Current thread 0xf7a45020 [python3.14] (most recent call first):
  File 
"/build/reproducible-path/python-memray-1.19.3+dfsg/.pybuild/cpython3_3.14_memray/build/tests/integration/test_object_tracking.py",
 line 346 in test_object_stack_trace_with_native_traces
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 167 in 
pytest_pyfunc_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 121 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 512 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1707 in runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 184 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 121 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 512 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 250 in <lambda>
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 361 in from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 249 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 139 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 118 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 121 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 512 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 408 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 121 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 512 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 384 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 330 in 
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 377 in 
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 121 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 512 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 229 in 
_main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 253 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 203 in _run_module_as_main

Current thread's C stack trace (most recent call first):
  <system returned no stack trace>

Extension modules: memray._memray, memray._test_utils, markupsafe._speedups 
(total: 3)
Segmentation fault
E: pybuild pybuild:485: test: plugin pyproject failed with: exit code=139: cd 
/build/reproducible-path/python-memray-1.19.3+dfsg/.pybuild/cpython3_3.14_memray/build;
 python3.14 -m pytest --ignore=tests/integration/test_main.py 
--ignore=tests/integration/test_native_tracking.py 
--ignore=tests/integration/test_tracing.py 
--ignore=tests/integration/test_tracking.py -v -k 'not test_thread_name and not 
test_setting_python_thread_name and not 
test_successful_parse_of_aggregated_capture_file and not 
test_reading_allocations_while_reading_stack_traces and not 
test_live_tracking_waits_for_client and not test_live_tracking and not 
test_live_client_exits_properly_on_sigint_before_connecting and not 
test_multithreaded_extension and not test_misbehaving_extension and not 
test_extension_that_uses_pygilstate_ensure and not test_native_dlopen and not 
test_valloc_at_thread_exit and not test_valloc_at_thread_exit_in_subprocess and 
not test_dlopen_with_rpath'

Regards,

Adam

--- End Message ---
--- Begin Message ---
Source: python-memray
Source-Version: 1.19.3+dfsg-2
Done: Colin Watson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
python-memray, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated python-memray package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 01 Jul 2026 12:51:12 +0100
Source: python-memray
Architecture: source
Version: 1.19.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1140692
Changes:
 python-memray (1.19.3+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Run tests with UNW_ARM_UNWIND_METHOD=4 on armhf (see #984706; closes:
     #1140692).
   * Standards-Version: 4.7.4.
Checksums-Sha1:
 e1fef23c9d2a953b6c5547751aa4cb1f16acea4b 3464 python-memray_1.19.3+dfsg-2.dsc
 b51d884208ef599700308c97c178becaa7fb54ab 12844 
python-memray_1.19.3+dfsg-2.debian.tar.xz
 c92cfe89bb8ddbcdb024453f3af102411d16e026 20540428 
python-memray_1.19.3+dfsg-2.git.tar.xz
 ca1aa06d75cae189fac229a06e26699f6dedafa4 17544 
python-memray_1.19.3+dfsg-2_source.buildinfo
Checksums-Sha256:
 ee9c29e4bced71da11f558505b2c12ff954bd0a265cae3d2a8a3a81684e3b911 3464 
python-memray_1.19.3+dfsg-2.dsc
 ee2ae2656d86ea9b24a8a046eea4cdc8d6f9e0a5b45d045a1bd9d3f58f9f000b 12844 
python-memray_1.19.3+dfsg-2.debian.tar.xz
 c63cfc949392c9bacd5120d7461f9012ac802ac152b5d186a8abc0ffca69bf16 20540428 
python-memray_1.19.3+dfsg-2.git.tar.xz
 754ba52200330d5d40f99048748bef2a7f77f6daa13c87b89df1fd06eefc031c 17544 
python-memray_1.19.3+dfsg-2_source.buildinfo
Files:
 25d16176d712a385819c50a62eab2d65 3464 python optional 
python-memray_1.19.3+dfsg-2.dsc
 77f4f334739c537850709aea43e33cea 12844 python optional 
python-memray_1.19.3+dfsg-2.debian.tar.xz
 c39a154a8889a2e99ddaf5f7d79d4f64 20540428 python None 
python-memray_1.19.3+dfsg-2.git.tar.xz
 94b2ee7bc38f91b2781800e94627bec3 17544 python optional 
python-memray_1.19.3+dfsg-2_source.buildinfo
Git-Tag-Info: tag=88d1e7c7d9f9d021194a1deb4561e742c90b8a11 
fp=ac0a4ff12611b6fccf01c111393587d97d86500b
Git-Tag-Tagger: Colin Watson <[email protected]>

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

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmpE/7EACgkQYG0ITkaD
wHkdFhAAxPjn3hd1r2olFLvKmFR+hEi0H5gCod+gbSE1HVuZYvIxrqeXrFsXi/Yc
cdedpA84mgqhVubdp10d+xM5nhkRamapZNPUwdMsuK2tdik7dKwwp3vQP81laF40
2ggJsA38AtHW3Vx7O8Hn3af25ym0Woz+AP1IQSHi/Nw+SB5mfc3NUTTCpvcjB0WA
pZWo4FVVKsJdE9lJxnva2PBsun4Zu5+kzMt0c2qDmyMz1jj0VTBxNWH3alfsHluG
jxKUv3WBaSdTNyzg92HtjokYVPpViD6AUfYi5QlhL9jCH2JZj74PUu8psDfHDMwT
kTpeYwGOU5HcjmYCzuzgUxuS1SF/l5bYr8YQV+OHJ1AQc66g3eZwc1X4T05RFFez
S9NrfHPqzBdfv7izu3aB5/NEwE1+57xMwYz5HXBjdBUAZV86sizV8bgQNZJ5ZYg2
Q6/635IJzvxfVXqhcuF1f8dhguaxVlRLoktgBcWn3q0lIWV1op/Kji9Ref5oD/OA
6hLbqapPoP/v43nWF9iZTgEcrZmUQWw5vVwcUhEWCbv1anP856Z4pJ/sjAYuSX/F
C4sCFoBZinVAZKzeb7nRZhPTJ6T3cdYsQKTwltyJqd7arRPQBJ4Wi+o8SYoglIAV
MLZWd6/9BtcY3nLUv46mzwlqts1UzysQ7YwXoXDcSUDmHx2wthU=
=bsK5
-----END PGP SIGNATURE-----

Attachment: pgpyAiKRLhoUq.pgp
Description: PGP signature


--- End Message ---

Reply via email to