automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: sunyang.wu@jaguarmicro.com, robot@bytheb.org
Subject: |FAILURE| pw127514 [PATCH v3 2/2] test/crypto: Add SM3/SM4 test vectors for verification in test app
Date: Thu, 25 May 2023 22:48:43 -0400	[thread overview]
Message-ID: <20230526024843.3994254-1-robot@bytheb.org> (raw)
In-Reply-To: <20230526011811.3628-2-sunyang.wu@jaguarmicro.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/127514/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5086292992
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
####################################################################################
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, 1 Changed (25 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added variables

1 function with some indirect sub-type change:

  [C] 'function int rte_cryptodev_get_auth_algo_enum(rte_crypto_auth_algorithm*, const char*)' at rte_cryptodev.c:365:1 has some indirect sub-type changes:
    parameter 1 of type 'rte_crypto_auth_algorithm*' has sub-type changes:
      in pointed to type 'enum rte_crypto_auth_algorithm' at rte_crypto_sym.h:314:1:
        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

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_cryptodev.so.23.1 install/usr/local/lib/x86_64-linux-gnu/librte_cryptodev.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 (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-----------------------------

      parent reply	other threads:[~2023-05-26  2:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230526011811.3628-2-sunyang.wu@jaguarmicro.com>
2023-05-26  1:08 ` |SUCCESS| pw127513-127514 " qemudev
2023-05-26  1:12 ` qemudev
2023-05-26  1:20 ` |SUCCESS| pw127514 " checkpatch
2023-05-26  2:48 ` 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=20230526024843.3994254-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).