Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #412133 > unrolled thread

Bug#1129609: python-memray: another autopkgtest failure causing ImportError unknown location

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1129609: python-memray: another autopkgtest failure causing ImportError unknown location Helmut Grohne <helmut@subdivi.de> - 2026-03-03 22:40 +0100
    Bug#1129609: marked as done (python-memray: another autopkgtest  failure causing ImportError unknown location) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-03-23 22:40 +0100

#412133 — Bug#1129609: python-memray: another autopkgtest failure causing ImportError unknown location

Source: python-memray
Version: 1.17.0+dfsg-1
Severity: serious

On top of the reported autopkgtest failure #1126944, there is another
one shadowing the former one. Some ecosystem change (pytest?) results in
tests failing to import memray:

|  57s ________________ ERROR collecting tests/integration/test_api.py ________________
|  57s ImportError while importing test module '/tmp/autopkgtest.ONqy8a/autopkgtest_tmp/tests/integration/test_api.py'.
|  57s Hint: make sure your test modules/packages have valid Python names.
|  57s Traceback:
|  57s /usr/lib/python3.14/importlib/__init__.py:88: in import_module
|  57s     return _bootstrap._gcd_import(name[level:], package, level)
|  57s            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|  57s tests/integration/test_api.py:5: in <module>
|  57s     from memray import FileDestination
|  57s /usr/lib/python3/dist-packages/memray/__init__.py:2: in <module>
|  57s     from ._memray import AllocationRecord
|  57s E   ImportError: cannot import name 'AllocationRecord' from 'memray._memray' (unknown location)

It is not clear why this happens now and didn't happen earlier. I tried
understanding it, but did not. What I did figure though was that if you
append "tests/" to the pytest invocation, this one gets fixed and we can
see #1126944 again.

On that other one, I spent some effort recorded in the upstream bug
tracker. At this time I suggest uploading libunwind with the
incompatible C++ exception support disabled. Before we can do that, this
failure needs to be fixed.

Helmut

[toc] | [next] | [standalone]

#414297 — Bug#1129609: marked as done (python-memray: another autopkgtest failure causing ImportError unknown location)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 23 Mar 2026 17:31:10 -0400
with message-id <acGxAG_GS2_t8zF-@grieg.kardiogramm.net>
and subject line Re: Bug#1129609: python-memray: another autopkgtest failure causing ImportError unknown location
has caused the Debian Bug report #1129609,
regarding python-memray: another autopkgtest failure causing ImportError unknown location
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 owner@bugs.debian.org
immediately.)


-- 
1129609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129609
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web