automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: arkadiuszx.kusztal@intel.com, robot@bytheb.org
Subject: |FAILURE| pw106965 [PATCH v2 4/4] crypto: reorganize endianness comments, add crypto uint
Date: Mon,  7 Feb 2022 08:39:02 -0500	[thread overview]
Message-ID: <20220207133902.12733-1-robot@bytheb.org> (raw)
In-Reply-To: <20220207113555.8431-5-arkadiuszx.kusztal@intel.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1806265088
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-18.04-gcc-shared-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
Error: ABI issue reported for 'abidiff --suppr devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/dump/librte_vhost.dump install/dump/librte_vhost.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
            type of 'anonymous data member union {rte_crypto_sym_op sym[]; rte_crypto_asym_op asym[];}' changed:
              type size hasn't changed
              1 data member change:
                type of 'rte_crypto_asym_op asym[]' changed:
                  array element type 'struct rte_crypto_asym_op' changed:
                    type size hasn't changed
                    1 data member changes (1 filtered):
                      type of 'anonymous data member union {rte_crypto_rsa_op_param rsa; rte_crypto_mod_op_param modex; rte_crypto_mod_op_param modinv; rte_crypto_dh_op_param dh; rte_crypto_dsa_op_param dsa; rte_crypto_ecdsa_op_param ecdsa; rte_crypto_ecpm_op_param ecpm;}' changed:
                        type size hasn't changed
                        1 data member changes (4 filtered):
                          type of 'rte_crypto_dsa_op_param dsa' changed:
                            type size changed from 832 to 1024 (in bits)
                            1 data member insertion:
                              'rte_crypto_uint rte_crypto_dsa_op_param::k', at offset 256 (in bits) at rte_crypto_asym.h:428:1
                            3 data member changes:
                              'rte_crypto_param rte_crypto_dsa_op_param::r' offset changed from 256 to 448 (in bits) (by +192 bits)
                              'rte_crypto_param rte_crypto_dsa_op_param::s' offset changed from 448 to 640 (in bits) (by +192 bits)
                              'rte_crypto_param rte_crypto_dsa_op_param::y' offset changed from 640 to 832 (in bits) (by +192 bits)
                  type size hasn't changed



##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

      parent reply	other threads:[~2022-02-07 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220207113555.8431-5-arkadiuszx.kusztal@intel.com>
2022-02-07 11:38 ` |SUCCESS| " checkpatch
2022-02-07 13:39 ` 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=20220207133902.12733-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=arkadiuszx.kusztal@intel.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).