Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)
On Sat, Apr 29, 2023 at 07:44:24PM +0530, Nilesh Patra wrote: > On Tue, Apr 18, 2023 at 03:54:23PM +0200, Andreas Tille wrote: > >2. Remove the package from testing for the moment. The only > > rdepends is currently pan-grazing-incidence which will be > > lowered to suggests once we re-render debian-pan metapackages. > > It is a possible option but it maybe a useful package in itself. > This numba situation has arised due to uploading a new upstream update > of genx during hard freeze (I wonder why this happened). I guess I understand the reason for this: > I think we do have a third alternative: > > > What do you think? > > 3. Cherry-pick the commit[6] for fixing this bug and upload to t-p-u by > asking release team first, or go ahead with a +really scheme whichever > seems better, but it needs to be done quickly. I guess I ended up under-estimating the fix. Even after applying heaps of patches, genx is rendering broken for me, in the sense that the GUI is up but I am observing some concerning warnings/errors in the logs, which means that I need to pick more and more commits to the point that the delta becomes huge for existing package. It probably _genuinely_ needs a new version that Roland uploaded, which had major rework and has fixes for many bugs. I think it is better out of bookworm at the moment. My 2 cents. > > [1] > >
Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)
On Tue, Apr 18, 2023 at 03:54:23PM +0200, Andreas Tille wrote: > and we have other errors for other architectures which all contain > the string "numba". IMHO this is a mess we can hardly fix in hard > freeze. I see only two chances: I haven't done a thorough research but it is probably originating from numba itself. >1. Restrict the architectures to amd64 and ppc64el (which are > the only ones where the build succeeds or We maybe a little too late for this as well. >2. Remove the package from testing for the moment. The only > rdepends is currently pan-grazing-incidence which will be > lowered to suggests once we re-render debian-pan metapackages. It is a possible option but it maybe a useful package in itself. This numba situation has arised due to uploading a new upstream update of genx during hard freeze (I wonder why this happened). I think we do have a third alternative: > What do you think? 3. Cherry-pick the commit[6] for fixing this bug and upload to t-p-u by asking release team first, or go ahead with a +really scheme whichever seems better, but it needs to be done quickly. > [1] >
Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)
Hi, I've found genx in the "Cleaner view"[1] due to missing builds[2]. It turns out that for instance for arm64[3] the build fails with tests/test_numba_equivalency.py Fatal Python error: Segmentation fault For armel[4] (and armhf) we get dh_auto_test -a -O--buildsystem=pybuild I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests Fatal Python error: Aborted Current thread 0xf7a30020 (most recent call first): File "/usr/lib/python3/dist-packages/llvmlite/binding/ffi.py", line 151 in __call__ File "/usr/lib/python3/dist-packages/llvmlite/binding/executionengine.py", line 92 in finalize_object File "/usr/lib/python3/dist-packages/numba/core/codegen.py", line 1060 in wrapper File "/usr/lib/python3/dist-packages/numba/core/codegen.py", line 999 in _finalize_specific File "/usr/lib/python3/dist-packages/numba/core/codegen.py", line 797 in _finalize_final_module ... For i386[5] I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests = test session starts == platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack rootdir: /<> collected 14 items / 1 error ERRORS _ ERROR collecting .pybuild/cpython3_3.11/build/tests/test_numba_equivalency.py _ tests/test_numba_equivalency.py:11: in from genx.models.lib import instrument, instrument_numba, paratt, paratt_numba, neutron_refl, neutron_numba, \ genx/models/lib/instrument_numba.py:9: in @numba.jit( /usr/lib/python3/dist-packages/numba/core/decorators.py:219: in wrapper disp.compile(sig) /usr/lib/python3/dist-packages/numba/core/dispatcher.py:965: in compile cres = self._compiler.compile(args, return_type) ... and we have other errors for other architectures which all contain the string "numba". IMHO this is a mess we can hardly fix in hard freeze. I see only two chances: 1. Restrict the architectures to amd64 and ppc64el (which are the only ones where the build succeeds or 2. Remove the package from testing for the moment. The only rdepends is currently pan-grazing-incidence which will be lowered to suggests once we re-render debian-pan metapackages. What do you think? Kind regards Andreas. [1]
