automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: kalesh-anakkur.purayil@broadcom.com, robot@bytheb.org
Subject: |FAILURE| pw106664 [dpdk-dev] [PATCH v7 4/4] doc: update release notes
Date: Fri, 28 Jan 2022 08:59:46 -0500	[thread overview]
Message-ID: <20220128135946.23949-1-robot@bytheb.org> (raw)
In-Reply-To: <20220128124830.427-5-kalesh-anakkur.purayil@broadcom.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1761549543
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
####################################################################################
              'rte_eth_event_type::RTE_ETH_EVENT_ERR_RECOVERING' value '11'
              'rte_eth_event_type::RTE_ETH_EVENT_RECOVERED' value '12'
            1 enumerator change:
              'rte_eth_event_type::RTE_ETH_EVENT_MAX' from value '11' to '13' at rte_ethdev.h:3793: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_ethdev.dump install/dump/librte_ethdev.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).



Skipped removed driver librte_crypto_octeontx2.dump.
Skipped removed driver librte_net_octeontx2.dump.
Functions changes summary: 0 Removed, 0 Changed (7 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Skipped removed driver librte_common_octeontx2.dump.
Skipped removed driver librte_event_octeontx2.dump.
Skipped removed driver librte_mempool_octeontx2.dump.
Functions changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Skipped removed driver librte_regex_octeontx2.dump.
Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added (18 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) 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:[~2022-01-28 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220128124830.427-5-kalesh-anakkur.purayil@broadcom.com>
2022-01-28 12:23 ` |SUCCESS| pw106664 " checkpatch
2022-01-28 13:59 ` 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=20220128135946.23949-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=kalesh-anakkur.purayil@broadcom.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).