From: Thomas Monjalon <thomas@monjalon.net>
To: Brandon Lo <blo@iol.unh.edu>
Cc: dev <dev@dpdk.org>, ci@dpdk.org
Subject: Re: [dpdk-ci] UNH-IOL ABI Failures
Date: Tue, 20 Apr 2021 17:37:19 +0200 [thread overview]
Message-ID: <1717688.4SEbdfRPfx@thomas> (raw)
In-Reply-To: <CAOeXdvbUU_G_m5kSh0i9BkDjK9R44gqauusWuQBgy5=AQu2KkQ@mail.gmail.com>
20/04/2021 17:30, Brandon Lo:
> Hi all,
>
> We have noticed some failures occurring repeatedly in our CI system
> regarding the ABI test.
>
> I looked into the failures and saw that there were some failures
> caused by a clock skew issue on the ARM ABI test.
> Those failures have been rerun and the report will be resent to
> patchworks for the updated result.
>
> However, the earlier test runs seem to report an actual failure:
>
> "1 function with some indirect sub-type change:
>
> [C]'function rte_security_session*
> rte_security_session_create(rte_security_ctx*,
> rte_security_session_conf*, rte_mempool*, rte_mempool*)' at
> rte_security.c:43:1 has some indirect sub-type changes:
> parameter 2 of type 'rte_security_session_conf*' has sub-type changes:
> in pointed to type 'struct rte_security_session_conf' at
> rte_security.h:366:1:
> type size hasn't changed
> 1 data member change:
> type of 'rte_crypto_sym_xform*
> rte_security_session_conf::crypto_xform' changed:
> in pointed to type 'struct rte_crypto_sym_xform' at
> rte_crypto_sym.h:575:1:
> type size hasn't changed
> 1 data member changes (1 filtered):
>
> Error: ABI issue reported for 'abidiff --suppr
> dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1
> reference/usr/local/include --headers-dir2 build/usr/local/include
> reference/dump/librte_security.dump build/dump/librte_security.dump'
>
> ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged
> this as a potential issue)."
>
> Can anyone please confirm that this is a real ABI issue or if this
> requires a change on the UNH-IOL side.
It requires libabigail 1.8 on UNH-IOL side.
next prev parent reply other threads:[~2021-04-20 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 15:30 Brandon Lo
2021-04-20 15:37 ` Thomas Monjalon [this message]
2021-04-20 17:02 ` Brandon Lo
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=1717688.4SEbdfRPfx@thomas \
--to=thomas@monjalon.net \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).