From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: jiaweiw@nvidia.com, robot@bytheb.org
Subject: |FAILURE| pw122695 [PATCH v2 2/2] ethdev: introduce the PHY affinity field in Tx queue API
Date: Mon, 30 Jan 2023 12:59:27 -0500 [thread overview]
Message-ID: <20230130175927.1870948-1-robot@bytheb.org> (raw)
In-Reply-To: <20230130170041.1360-3-jiaweiw@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/122695/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4046424090
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
2 functions with some indirect sub-type change:
[C] 'function int rte_eth_dev_info_get(uint16_t, rte_eth_dev_info*)' at rte_ethdev.c:3307:1 has some indirect sub-type changes:
parameter 2 of type 'rte_eth_dev_info*' has sub-type changes:
in pointed to type 'struct rte_eth_dev_info' at rte_ethdev.h:1723:1:
type size hasn't changed
1 data member change:
type of 'rte_eth_txconf default_txconf' changed:
type size hasn't changed
1 data member insertion:
'uint8_t tx_phy_affinity', at offset 72 (in bits) at rte_ethdev.h:1147:1
[C] 'function int rte_eth_tx_queue_info_get(uint16_t, uint16_t, rte_eth_txq_info*)' at rte_ethdev.c:5281:1 has some indirect sub-type changes:
parameter 3 of type 'rte_eth_txq_info*' has sub-type changes:
in pointed to type 'struct rte_eth_txq_info' at rte_ethdev.h:1822:1:
type size hasn't changed
no data member change (1 filtered);
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).
Functions changes summary: 0 Removed, 0 Changed (2 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+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-01-30 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230130170041.1360-3-jiaweiw@nvidia.com>
2023-01-30 16:57 ` |SUCCESS| pw122696-122695 " qemudev
2023-01-30 17:01 ` qemudev
2023-01-30 17:02 ` |SUCCESS| pw122695 " checkpatch
2023-01-30 17: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=20230130175927.1870948-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=jiaweiw@nvidia.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).