From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: sunyang.wu@jaguarmicro.com, robot@bytheb.org
Subject: |FAILURE| pw127397 [PATCH v2 2/2] test/crypto: Add SM3/SM4 test vectors for verification in test app
Date: Thu, 25 May 2023 07:19:56 -0400 [thread overview]
Message-ID: <20230525111956.1225296-1-robot@bytheb.org> (raw)
In-Reply-To: <20230525100806.36992-2-sunyang.wu@jaguarmicro.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/127397/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5078825231
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
1 data member changes (1 filtered):
type of 'anonymous data member union {rte_crypto_auth_xform auth; rte_crypto_cipher_xform cipher; rte_crypto_aead_xform aead;}' changed:
type size hasn't changed
1 data member changes (1 filtered):
type of 'rte_crypto_auth_xform auth' changed:
type size hasn't changed
1 data member change:
type of 'rte_crypto_auth_algorithm algo' changed:
type size hasn't changed
1 enumerator insertion:
'rte_crypto_auth_algorithm::RTE_CRYPTO_AUTH_SM3_HMAC' value '30'
2 enumerator changes:
'rte_crypto_auth_algorithm::RTE_CRYPTO_AUTH_SHAKE_128' from value '30' to '31' at rte_crypto_sym.h:314:1
'rte_crypto_auth_algorithm::RTE_CRYPTO_AUTH_SHAKE_256' from value '31' to '32' at rte_crypto_sym.h:314:1
type size hasn't changed
Error: ABI issue reported for abidiff --suppr /home/runner/work/dpdk/dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/usr/local/lib/x86_64-linux-gnu/librte_vhost.so.23.1 install/usr/local/lib/x86_64-linux-gnu/librte_vhost.so.23.2
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed, 0 Changed (10 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (7 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-05-25 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230525100806.36992-2-sunyang.wu@jaguarmicro.com>
2023-05-25 10:09 ` |SUCCESS| " checkpatch
2023-05-25 10:22 ` |SUCCESS| pw127395-127397 " qemudev
2023-05-25 10:26 ` qemudev
2023-05-25 11:19 ` 0-day Robot [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=20230525111956.1225296-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=sunyang.wu@jaguarmicro.com \
--cc=test-report@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).