test_lambdify.py unit test fails when using symengine compiled with tcmalloc
#475
Comments
|
Here is a backtrace after running above example: |
|
Could I provide anything else to help debug this issue? |
|
Can you try symengine/symengine#2071 with tcmalloc? |
No, that patch doesn't seem to solve the issue for me. Some of the unit tests included in this repo also fail with tcmalloc. In particular, this one: symengine.py/symengine/tests/test_lambdify.py Line 572 in e21a4e9 Perhaps it is easier for you to debug than the original issue with qiskit. Or here is a self-contain script that produces a crash: import symengine as se
import sympy as sp
cb = sp.lambdify
Mtx = sp.Matrix
x, y = se.symbols('x, y')
args = Mtx(2, 1, [x, y])
v = Mtx(2, 1, [x**3 * y, (x+1)*(y+1)])
jac = v.jacobian(args)
exprs = [jac, x+y, v, (x+1)*(y+1)]
lmb = cb(args, exprs) # Crashes here |
iyanmv
changed the title
qiskit unit tests fail when using symengine with tcmalloctest_lambdify.py unit test fails when using symengine compiled with tcmalloc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Edited description (Jan 19, 2025)
Test
test_lambdify__sympy()from test_lambdify.py fails when sympy is installed and symengine was compiled withWITH_TCMALLOC=ON.Minimal example:
This crashes for me with:
Bug in Arch Linux package: https://gitlab.archlinux.org/archlinux/packaging/packages/python-symengine/-/issues/2
Original description (May 11, 2024)
Some tests from
qiskitwork fine when usingsymenginefrom PyPI but failed when usingsymengineandpython-symenginefrom the Arch Linux repos. After using [the same PKGBUILD] to rebuild the packages but just disablingtcmallocthe tests don't crash anymore.I've reported this in
qiskitrepo (Qiskit/qiskit#12359) but they think it's asymenginebug.Here is a minimal example that can produce the crash affecting the unit tests:
This same example works fine when
symegineis compiled withouttcmalloc. Curiously, if one importssymenginein the same script, it also works (even withsymenginewithtcmalloc):Perhaps some extra 👀 from here can help understand this issue better :) Also, can you clarify if the recommended way to create packages for distros is to use
tcmallocor not? Arch usestcmallocbut also-DWITH_SYMENGINE_THREAD_SAFE=ON. I guess it's a mixture of the flags recommended for distros and the optimized build. Is this properly tested? I noticed that the official wheel packages for PyPI, for example, do not usetcmalloc.The text was updated successfully, but these errors were encountered: