test_benchmarks.py Fatal Python error: Aborted #11
Comments
|
Can't reproduce on all my test platforms (CentOS, Ubuntu, ...). See here for example. What would you recommend as the easiest way of reproducing this? |
|
Thanks for your reply. First I am not the maintainer of the package but just as a member of Debian Python Team to try to fix the ftbfs issue. Because the original maintainer of the package did not create a repo for it, so I just create its' debian repo to debug the issue easily for us.:) Before your deep debug on Debian build environment, I suspect the build dependences of plotpy that has issue. For 2.2.0, the debian/control has the build dependences is below: Using the same B-D, the 2.3.2 will be failed with the same reason. As I update the debian/control, now it will be hang without anything output. |
|
Thanks for the additional details. I'm adding this task to the to-do list with the highest priority. |
|
Hi @yuzibo , Could you please help me reproduce this issue? I have created a VM based on the latest Debian Unstable ISO. Here is what I've done. # At this point, this is a fresh install of Debian Unstable
nano /etc/apt/sources.list # to add `deb http://deb.debian.org/debian/ unstable main non-free-firmware`
sudo apt-get update
git clone https://github.com/PlotPyStack/PlotPy.git
cd PlotPy/
sudo apt-get install dh-python cython3 python3-all python3-guidata python3-numpy python3-scipy python3-qwt python3-pytest python3-all-dev
python3 setup.py build_ext --inplace
pytest |
|
Hi @PierreRaybaut, thanks for your work here, appreciate it! To reproduce this issue, we have to setup Debian packaging env, let me try simply to setup it. On Debian unstable: Once got the log, the schroot was created successfully. If target for 2.2.0, see #1071775, just Then you should see the result was the same with #1071775. If target for 2.3.2, please git clone my repo salsa first: you will have to install some gbp something here. If debug the package env during packaging, you can: Sorry, maybe there are too many Debian stuff for you. Thank you very much for this again. Please let me know if any issue and next two days I should have some time on this. |
|
Hi, Seems to be that iterator is deprecated. Similar issue here iree-org/iree@88b1d4d |
Thanks for the feedback. |
Hey @yuzibo , So I've tried to follow the steps of the first part of your instructions. pierre@DebianTesting:~/plotpy-2.2.0$ sudo sbuild -c sid-amd64-sbuild --no-clean
dpkg-source: info: using options from plotpy-2.2.0/debian/source/options: --extend-diff-ignore=^[^/]+.(egg-info|dist-info)/
dpkg-source: info: using options from plotpy-2.2.0/debian/source/options: --extend-diff-ignore=^[^/]+.(egg-info|dist-info)/
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building plotpy using existing ./plotpy_2.2.0.orig.tar.gz
dpkg-source: info: building plotpy in plotpy_2.2.0-3.debian.tar.xz
dpkg-source: info: building plotpy in plotpy_2.2.0-3.dsc
dpkg-source: info: using options from plotpy-2.2.0/debian/source/options: --extend-diff-ignore=^[^/]+.(egg-info|dist-info)/
sbuild (Debian sbuild) 0.85.10 (30 May 2024) on DebianTesting.myguest.virtualbox.org
+==============================================================================+
| plotpy 2.2.0-3 (amd64) Tue, 18 Jun 2024 08:39:13 +0000 |
+==============================================================================+
Package: plotpy
Version: 2.2.0-3
Source Version: 2.2.0-3
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace 'var/run/schroot/mount/sid-amd64-sbuild-23cfc17d-90c9-4035-a1fe-3ee1e560c658' with '<<CHROOT>>'
I: NOTICE: Log filtering will replace 'build/plotpy-qHDBUm/resolver-0Sj5LE' with '<<RESOLVERDIR>>'
+------------------------------------------------------------------------------+
| Update chroot |
+------------------------------------------------------------------------------+
Get:1 http://deb.debian.org/debian sid InRelease [198 kB]
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Sub-process apt-key returned an error code (29)Err:1 http://deb.debian.org/debian sid InRelease
gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
Reading package lists...
W: GPG error: http://deb.debian.org/debian sid InRelease: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
E: The repository 'http://deb.debian.org/debian sid InRelease' is not signed.
E: apt-get update failed
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
Build Architecture: amd64
Build Type: binary
Build-Space: 0
Build-Time: 0
Distribution: unstable
Fail-Stage: apt-get-update
Host Architecture: amd64
Install-Time: 0
Job: /home/pierre/plotpy_2.2.0-3.dsc
Machine Architecture: amd64
Package: plotpy
Package-Time: 0
Source-Version: 2.2.0-3
Space: 0
Status: failed
Version: 2.2.0-3
--------------------------------------------------------------------------------
Finished at 2024-06-18T08:39:13Z
Build needed 00:00:00, 0k disk space
E: apt-get update failedAny idea? |
|
hi, Could you try it with the instructions? To enter into chroot env, we have to In fact, I do not remember I have faced the issue on my physical host. but maybe we can try it. |
|
Just did it: But, unfortunately, same result as before. |
|
There may be an issue with the permissions of |
|
I think we can change permissions of Under chroot with |
|
Sorry, my bad, that's because I needed to remove and recreate it to change the first "-" into "c" in permissions: So now, the building process is running smoothly... (in progress) |
|
OK, so now I have exactly the same output as you first posted. Now I'm wondering how I could debug this. |
|
Maybe we try it with the below . see the later of the comment : It will fail again at the same place with the same dependences from Debian packaging. But because we are undering the chroot, so we can do anything we want to debug. Sorry, I have little knowledge about Python debug, so this is my goal to ask for help from you here.:) |
|
Quick question, when I'm under chroot environment, I loose my user home directory: Is it normal? Do I have to mount it manually? |
|
hmm, maybe I forget to mention it. change to |
|
OK, so here is the real traceback: This On Ubuntu, I usually do the following to fix this: |
|
So basically, I think that solving this whole issue will simply be done by installing the right (missing) Debian package(s). |
|
Now, that I have the VM configured, I may test any additional package install to check if that solves the issue. |
|
Great.
|
|
OK, everything works after doing this: Here is the output of |
|
Okay, I can test it my side. Could you try on a clean build env? It passed python3.12 but not python3.11: |
|
Oh, by the way, I should have mentioned it earlier but (...actually it appears that |
I'm looking into it. |
|
OK, I can reproduce it. But then, when I echo the QT_QPA_PLATFORM, it seems to be undefined. |
|
🎉 I just found out where it comes from! (this is a teaser 😉) |
|
\o/. That is really good news. yeah, I can backport the commit to Debian side or just waiting new release. And I am waiting for the original maintainer of the Debian package to allow me to create salsa repo under Debian Python Team, then I can do more things for this package. But fixing bug with upstream is always good things.:) Cheers, |
|
Hi guys, one of the Debian maintainers for both plotpy and python-qwt here. I updated the package for python-qwt to v0.12.5, but I still see the Fatal Python error: Aborted error when building plotpy with it. Even updating plotpy to 2.3.5 doesn't seem to help. |
|
Hi @rolandmas, how can I reproduce this to help figure out what's going on? |
|
@yuzibo Please use the https://salsa.debian.org/python-team/packages/plotpy repository for collaboration :-) |
|
Ah, it seems I missed some info. Let me retry with your QT_QPA_PLATFORM trick. |
|
I sure hope that it works... I was so glad to finally fix this (and it took quite some time to figure it out). |
|
Nope, still fails: I noticed guidata in there, so tried to update guidata to a more recent version too, but… building guidata 3.5.2 also fails (in the testsuite) with a similar error, on a similar |
|
That is not the same issue because it's failing when executing the very first test which shows a Qt widget. |
|
@rolandmas : to clarify my previous comment, if tests are failing (for guidata or plotpy) when If it persists after having done the following, please get back to me with some instructions to reproduce the issue and I will gladly help: |
|
Hi all, It seems @rolandmas has fixed the issue from the repo he has pushed. I just built it.:) So I think we can close the issue again. BR, |
|
Even with both workarounds (export QT_QPA_PLATFORM=offscreen + x11-utils), plotpy 2.3.5 and guidata 3.5.2 still fail for me (in a clean, up-to-date, unstable cowbuilder chroot). (datalab 0.16.1 also seems to fail, but apparently for another reason; I'll open a ticket in the appropriate place once I get the full build log) |
|
For some reason, installing dbus fixes the build for plotpy (even without x11-utils and the environment variable). So plotpy 2.3.5-1 is on its way to Debian :-) The guidata testsuite fails differently with that addition, but I'll investigate further. |
|
…and guidata also works with dbus, provided the packaging is updated to reflect the renaming of the GUIDATA_UNATTENDED_TESTS variable to GUIDATA_UNATTENDED. So guidata 3.5.2-1 is on its way to unstable. This ticket can be closed as far as I'm concerned :-) |
|
@rolandmas : regarding guidata, you shouldn't need to set the GUIDATA_UNATTENDED environment variable if |
Hi,
There is one ftbfs issue on Debian:
The full log is here and I tested it on 2.3.2 failed also.
The text was updated successfully, but these errors were encountered: