automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: ndabilpuram@marvell.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw96850 [dpdk-dev] [PATCH v4 4/4] doc: remove deprecation notice for security fast path change
Date: Thu, 12 Aug 2021 08:58:59 -0400	[thread overview]
Message-ID: <20210812125859.9176-1-robot@bytheb.org> (raw)
In-Reply-To: <20210812123257.19595-5-ndabilpuram@marvell.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1123900482
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
####################################################################################

1 function with some indirect sub-type change:

  [C] 'function const rte_security_capability* rte_security_capabilities_get(rte_security_ctx*)' at rte_security.c:156:1 has some indirect sub-type changes:
    parameter 1 of type 'rte_security_ctx*' has sub-type changes:
      in pointed to type 'struct rte_security_ctx' at rte_security.h:67:1:
        type size hasn't changed
        1 data member insertion:
          'uint32_t rte_security_ctx::flags', at offset 160 (in bits) at rte_security.h:74:1

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_security.dump install/dump/librte_security.dump'


ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
ABIDIFF_ABI_INCOMPATIBLE_CHANGE, this change breaks the ABI.
Functions changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (33 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (54 filtered out), 0 Added (11 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

##[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:[~2021-08-12 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210812123257.19595-5-ndabilpuram@marvell.com>
2021-08-12 12:35 ` [dpdk-test-report] |SUCCESS| pw96850 " checkpatch
2021-08-12 12:58 ` 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=20210812125859.9176-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=ndabilpuram@marvell.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).