DPDK CI discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: 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 16:02:13 +0200
Message-ID: <CAJFAV8xe4DhpdKFBNQrXTymU4D8XVhaZPmeDpXMfFCv96uXR-g@mail.gmail.com> (raw)
In-Reply-To: <CAOE1vsMnW2SVgocb3hRpdgNG41hDnmeAyTq+X7TfSYCCkXGCLw@mail.gmail.com>

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.

David Marchand

  reply	other threads:[~2021-06-04 14:02 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 [this message]
2021-06-04 18:28     ` Owen Hilyard
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:

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

  git send-email \
    --in-reply-to=CAJFAV8xe4DhpdKFBNQrXTymU4D8XVhaZPmeDpXMfFCv96uXR-g@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --cc=mdr@ashroe.eu \
    --cc=thomas@monjalon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ https://inbox.dpdk.org/ci \
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git