Re: [help] New error in test cases of bmtk

2021-11-22 Thread Andrey Rahmatullin
On Mon, Nov 22, 2021 at 01:27:23PM +0100, Andreas Tille wrote:
> Hi,
> 
> I think I've found a patch[1] to solve the original issue which just
> seems to be a floating point precision issue.  However, meanwhile there
> is another less simple issue:
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connection_map.py _
> ImportError while importing test module 
> '/build/bmtk-0.0.9+ds/.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connection_map.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3/dist-packages/pandas/__init__.py:30: in 
> from pandas._libs import hashtable as _hashtable, lib as _lib, tslib as 
> _tslib
> /usr/lib/python3/dist-packages/pandas/_libs/__init__.py:13: in 
> from pandas._libs.interval import Interval
> E   ModuleNotFoundError: No module named 'pandas._libs.interval'
You need to wait until it's built for 3.10.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


[help] New error in test cases of bmtk

2021-11-22 Thread Andreas Tille
Hi,

I think I've found a patch[1] to solve the original issue which just
seems to be a floating point precision issue.  However, meanwhile there
is another less simple issue:

 ERRORS 
_ ERROR collecting 
.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connection_map.py _
ImportError while importing test module 
'/build/bmtk-0.0.9+ds/.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connection_map.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/pandas/__init__.py:30: in 
from pandas._libs import hashtable as _hashtable, lib as _lib, tslib as 
_tslib
/usr/lib/python3/dist-packages/pandas/_libs/__init__.py:13: in 
from pandas._libs.interval import Interval
E   ModuleNotFoundError: No module named 'pandas._libs.interval'

The above exception was the direct cause of the following exception:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
bmtk/tests/builder/test_connection_map.py:4: in 
from bmtk.builder.connection_map import ConnectionMap
bmtk/builder/__init__.py:23: in 
from .networks import DenseNetwork, NetworkBuilder
bmtk/builder/networks/__init__.py:23: in 
from .dm_network import DenseNetwork
bmtk/builder/networks/dm_network.py:32: in 
from bmtk.utils import sonata
bmtk/utils/sonata/__init__.py:24: in 
from .file import File
bmtk/utils/sonata/file.py:23: in 
from . import utils
bmtk/utils/sonata/utils.py:27: in 
import pandas as pd
/usr/lib/python3/dist-packages/pandas/__init__.py:34: in 
raise ImportError(
E   ImportError: C extension: No module named 'pandas._libs.interval' not 
built. If you want to import pandas from the source directory, you may need to 
run 'python setup.py build_ext --
_ ERROR collecting 
.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connector.py _
ImportError while importing test module 
'/build/bmtk-0.0.9+ds/.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connector.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/pandas/__init__.py:30: in 
from pandas._libs import hashtable as _hashtable, lib as _lib, tslib as 
_tslib
/usr/lib/python3/dist-packages/pandas/_libs/__init__.py:13: in 
from pandas._libs.interval import Interval
E   ModuleNotFoundError: No module named 'pandas._libs.interval'

The above exception was the direct cause of the following exception:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
bmtk/tests/builder/test_connector.py:1: in 
from bmtk.builder import connector
bmtk/builder/__init__.py:23: in 
from .networks import DenseNetwork, NetworkBuilder
bmtk/builder/networks/__init__.py:23: in 
from .dm_network import DenseNetwork
bmtk/builder/networks/dm_network.py:32: in 
from bmtk.utils import sonata
bmtk/utils/sonata/__init__.py:2= test session 
starts ==


I updated the upstream version in Git (but the issue is the same for the version
in unstable) and you can see a full build log in Salsa CI[2].

Any idea how to fix this?

Kind regards

  Andreas.


[1] 
https://salsa.debian.org/med-team/bmtk/-/blob/master/debian/patches/precision_in_test.patch
[2] https://salsa.debian.org/med-team/bmtk/-/jobs/2206233#L2178

-- 
http://fam-tille.de