On 2024-05-24 15:41, Georges Khaznadar wrote:
Hello Drew,
I could not reproduce with my machine the issue which you are
describing:
- I installed python3-scipy 1.12.0-1exp3 over 1.11.4-10
- I launched the test suite :
$ cd ~/<some_path>/pysatellites
~/<some_path>/pysatellites$ make
pyuic5 pysat.ui -o UI_pysat.py
pyuic5 graphe.ui -o UI_graphe.py
~/<some_path>/pysatellites$ debian/tests/runtests.sh
============================= test session starts
==============================
platform linux -- Python 3.11.9, pytest-7.4.4, pluggy-1.5.0
PyQt5 5.15.10 -- Qt runtime 5.15.10 -- Qt compiled 5.15.10
rootdir: ~/<some_path>/pysatellites
plugins: filter-subpackage-0.2.0, mock-3.12.0, arraydiff-0.6.1,
doctestplus-1.2.1, anyio-4.3.0, astropy-header-0.2.2,
hypothesis-6.102.1, typeguard-4.1.5, openfiles-0.5.0, remotedata-0.4.1,
qt-4.3.1
collected 2 items
debian/tests/test_gui.py .
[ 50%]
debian/tests/test_trajectoire.py .
[100%]
============================== 2 passed in 12.17s
==============================
... with no error.
Is there another trick to reproduce the bug?
I'm not sure. I'm just reporting debci results,
https://ci.debian.net/packages/p/pysatellites/unstable/arm64/
https://ci.debian.net/packages/p/pysatellites/unstable/arm64/46974597/
Just to be sure, the problem is on arm64, not amd64.
Perhaps it's a transient failure that we won't see after the upload to
unstable.
Thanks for checking it anyway.
