From: David Marchand <david.marchand@redhat.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Timothy McDaniel <timothy.mcdaniel@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Ray Kinsella <mdr@ashroe.eu>, Aaron Conole <aconole@redhat.com>,
dpdklab <dpdklab@iol.unh.edu>,
"abhinandan.gujjar@intel.com" <abhinandan.gujjar@intel.com>,
"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>,
dev <dev@dpdk.org>, Shijith Thotton <sthotton@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"mattias.ronnblom@ericsson.com" <mattias.ronnblom@ericsson.com>,
ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-dev] [pull-request] dpdk-next-net-eventdev - 21.05 - PRE-RC1
Date: Tue, 13 Apr 2021 11:14:03 +0200 [thread overview]
Message-ID: <CAJFAV8zF0ySz+hTOGP1Na1Q+4gjQY683AGJ0ZnZbKjcpjGAhfA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yRd1uFoV29VdEkoQ_XPPxPdAvTLMes7=Fzy3tCkzapPA@mail.gmail.com>
On Tue, Apr 13, 2021 at 11:07 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Tue, Apr 13, 2021 at 10:55 AM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> > I was running the following script[1] to detect ABI issues.
> > Since the "./devtools/test-meson-builds.sh" did not return non zero value or
> > the error print was "Error: cannot find librte_event_dlb.dump", It is
> > missed from my side.
> >
> > @David Marchand @Thomas Monjalon Could you share the snippet you are
> > using for detecting the ABI issue.
> >
> >
> > ------------------------
> > # ABI check
> > DPDK_ABI_REF_VERSION=v20.11 DPDK_ABI_REF_DIR=/tmp bash
>
> Ah ok, this is because event/dlb did not exist in 20.11.
> Running against 21.02, you should get the error.
Clicked send too quickly...
No, it did exist.
$ DPDK_ABI_REF_VERSION=v20.11 ./devtools/test-meson-builds.sh
ninja: Entering directory `/home/dmarchan/builds/build-gcc-static'
ninja: no work to do.
ninja: Entering directory `/home/dmarchan/builds/build-gcc-shared'
ninja: no work to do.
Error: cannot find librte_event_dlb.dump in
/home/dmarchan/builds/build-gcc-shared/install
Hum... the next reason I see would be that your reference does not
have event/dlb which is surprising with default configuration.
$ ls $DPDK_ABI_REF_DIR/*/*/dump/*dlb.dump
/home/dmarchan/abi/v20.11/build-clang-shared/dump/librte_event_dlb.dump
/home/dmarchan/abi/v21.02/build-clang-shared/dump/librte_event_dlb.dump
/home/dmarchan/abi/v20.11/build-gcc-shared/dump/librte_event_dlb.dump
/home/dmarchan/abi/v21.02/build-gcc-shared/dump/librte_event_dlb.dump
--
David Marchand
next prev parent reply other threads:[~2021-04-13 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SN7PR18MB4398B6507C1A0567260158CDC8709@SN7PR18MB4398.namprd18.prod.outlook.com>
[not found] ` <3565653.Ar8n8QqFrN@thomas>
2021-04-13 7:15 ` David Marchand
2021-04-13 7:31 ` Thomas Monjalon
2021-04-13 8:54 ` Jerin Jacob
2021-04-13 9:01 ` Thomas Monjalon
2021-04-13 9:07 ` David Marchand
2021-04-13 9:12 ` Thomas Monjalon
2021-04-13 9:14 ` David Marchand [this message]
2021-04-13 12:58 ` Aaron Conole
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=CAJFAV8zF0ySz+hTOGP1Na1Q+4gjQY683AGJ0ZnZbKjcpjGAhfA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=abhinandan.gujjar@intel.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=gakhil@marvell.com \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@marvell.com \
--cc=thomas@monjalon.net \
--cc=timothy.mcdaniel@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).