Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Bob Pearson <rpearsonhpe@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: warnings from pyverbs tests
Date: Mon, 4 Apr 2022 14:31:47 -0500	[thread overview]
Message-ID: <dcbe5883-2c04-617e-cc3a-5680ca6d823c@gmail.com> (raw)
In-Reply-To: <20220404184444.GR2120790@nvidia.com>

On 4/4/22 13:44, Jason Gunthorpe wrote:
> On Mon, Apr 04, 2022 at 01:19:21PM -0500, Bob Pearson wrote:
>> 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.
> 
> 
> 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.

      reply	other threads:[~2022-04-04 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 18:19 warnings from pyverbs tests Bob Pearson
2022-04-04 18:44 ` Jason Gunthorpe
2022-04-04 19:31   ` Bob Pearson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dcbe5883-2c04-617e-cc3a-5680ca6d823c@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox