From: Owen Hilyard <ohilyard@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
dpdklab <dpdklab@iol.unh.edu>,
ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-ci] [dpdklab] ABI test failing for openSUSE and Arch Linux
Date: Fri, 4 Jun 2021 14:28:49 -0400 [thread overview]
Message-ID: <CAHx6DYCwyk6DFBf0f+LTR+2JTe+s46qJF=CmXV4eObK6DYpM-Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xe4DhpdKFBNQrXTymU4D8XVhaZPmeDpXMfFCv96uXR-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
All,
The ABI reference seems to have been generated incorrectly. After
re-generating the ABI reference and re-running all of the patches, ABI
passed for all affected patches.
Owen Hilyard
On Fri, Jun 4, 2021 at 10:02 AM David Marchand <david.marchand@redhat.com>
wrote:
> On Fri, Jun 4, 2021 at 3:53 PM Lincoln Lavoie <lylavoie@iol.unh.edu>
> wrote:
> >
> > All,
> >
> > The ABI references for all systems were updated this week to the 21.05
> release code. The two failures look like places where the interfaces
> didn't actually change. We do see the failures across multiple patches,
> which might imply something got merged that caused these changes / failures.
>
> I checked ABI for 64307fad7d2b ("telemetry: remove static limit on
> callbacks count") against v21.05, yesterday.
> There is no issue.
>
> The report I mentioned
> https://lab.dpdk.org/results/dashboard/patchsets/17309/ is for a patch
> added on top of 64307fad7d2b.
> And the patch for this patchset won't break ABI.
>
>
> Can you confirm the ABI check runs fine against the main repo?
> I can't find a report for it in lab.dpdk.org.
> https://lab.dpdk.org/results/dashboard/tarballs/
>
>
> --
> David Marchand
>
>
[-- Attachment #2: Type: text/html, Size: 1959 bytes --]
next prev parent reply other threads:[~2021-06-04 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 7:58 [dpdk-ci] " David Marchand
2021-06-04 13:52 ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2021-06-04 14:02 ` David Marchand
2021-06-04 18:28 ` Owen Hilyard [this message]
2021-06-07 8:33 ` David Marchand
2021-06-09 15:07 ` Brandon Lo
2021-06-10 8:02 ` David Marchand
2021-06-10 8:13 ` Lincoln Lavoie
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='CAHx6DYCwyk6DFBf0f+LTR+2JTe+s46qJF=CmXV4eObK6DYpM-Q@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dpdklab@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
/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).