warnings from pyverbs tests
Back from vacation I see the following warnings when I run the pyverbs test suite.
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.device.Context size changed, may indicate binary incompatibility. Expected 160 from C header, got 176 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPEx size changed, may indicate binary incompatibility. Expected 136 from C header, got 144 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPInitAttrEx size changed, may indicate binary incompatibility. Expected 208 from C header, got 216 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.PD size changed, may indicate binary incompatibility. Expected 128 from C header, got 136 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.ParentDomain size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.providers.mlx5.mlx5dv.Mlx5Context size changed, may indicate binary incompatibility. Expected 192 from C header, got 200 from PyObject
It seems the headers in rdma-core and the kernel are out of sync. I just pulled fresh bits from both.
Bob
Jason Gunthorpe
maintainerQuoted 8 lines · Bob Pearson
Back from vacation I see the following warnings when I run the pyverbs test suite.
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.device.Context size changed, may indicate binary incompatibility. Expected 160 from C header, got 176 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPEx size changed, may indicate binary incompatibility. Expected 136 from C header, got 144 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPInitAttrEx size changed, may indicate binary incompatibility. Expected 208 from C header, got 216 from PyObject
Quoted 8 lines
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.PD size changed, may indicate binary incompatibility. Expected 128 from C header, got 136 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.ParentDomain size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.providers.mlx5.mlx5dv.Mlx5Context size changed, may indicate binary incompatibility. Expected 192 from C header, got 200 from PyObject
It seems the headers in rdma-core and the kernel are out of sync. I just pulled fresh bits from both.
I don't think it has to do with kernel, that looks like a python compilation problem. Rebuild a fresh rdma-core and make sure it is not mixing and matching shared librarie somehow
Jason
Quoted 16 lines · Jason Gunthorpe
Quoted 15 lines · Bob Pearson
Back from vacation I see the following warnings when I run the pyverbs test suite.
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.device.Context size changed, may indicate binary incompatibility. Expected 160 from C header, got 176 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPEx size changed, may indicate binary incompatibility. Expected 136 from C header, got 144 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPInitAttrEx size changed, may indicate binary incompatibility. Expected 208 from C header, got 216 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.PD size changed, may indicate binary incompatibility. Expected 128 from C header, got 136 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.ParentDomain size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject
<frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.providers.mlx5.mlx5dv.Mlx5Context size changed, may indicate binary incompatibility. Expected 192 from C header, got 200 from PyObject
Quoted 8 lines
Quoted 1 line
It seems the headers in rdma-core and the kernel are out of sync. I just pulled fresh bits from both.
I don't think it has to do with kernel, that looks like a python compilation problem. Rebuild a fresh rdma-core and make sure it is not mixing and matching shared librarie somehow
Jason
I removed rdma-core/build and rebuilt everything. That fixed it.
Thanks.