From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: roretzla@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw137311 [PATCH v6 23/23] devtools: forbid new use of rte marker typedefs
Date: Tue, 27 Feb 2024 01:45:31 -0500 [thread overview]
Message-ID: <20240227064531.325618-1-robot@bytheb.org> (raw)
In-Reply-To: <1709012499-12813-24-git-send-email-roretzla@linux.microsoft.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/137311/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8060384473
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
[C] 'function const rte_eth_rxtx_callback* rte_eth_add_first_rx_callback(uint16_t, uint16_t, rte_rx_callback_fn, void*)' at rte_ethdev.c:5768:1 has some indirect sub-type changes:
parameter 3 of type 'typedef rte_rx_callback_fn' has sub-type changes:
underlying type 'typedef uint16_t (typedef uint16_t, typedef uint16_t, rte_mbuf**, typedef uint16_t, typedef uint16_t, void*)*' changed:
in pointed to type 'function type typedef uint16_t (typedef uint16_t, typedef uint16_t, rte_mbuf**, typedef uint16_t, typedef uint16_t, void*)':
parameter 3 of type 'rte_mbuf**' has sub-type changes:
in pointed to type 'rte_mbuf*':
in pointed to type 'struct rte_mbuf' at rte_mbuf_core.h:470:1:
type size hasn't changed
4 data member deletions:
'RTE_MARKER cacheline0', at offset 0 (in bits) at rte_mbuf_core.h:467:1
'RTE_MARKER64 rearm_data', at offset 128 (in bits) at rte_mbuf_core.h:490:1
'RTE_MARKER rx_descriptor_fields1', at offset 256 (in bits) at rte_mbuf_core.h:517:1
'RTE_MARKER cacheline1', at offset 512 (in bits) at rte_mbuf_core.h:598:1
no data member change (1 filtered);
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/librte_ethdev.so.24.0 install/usr/local/lib/librte_ethdev.so.24.1
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed, 0 Added (2 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-02-27 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709012499-12813-24-git-send-email-roretzla@linux.microsoft.com>
2024-02-27 5:21 ` |SUCCESS| pw137295-137311 " qemudev
2024-02-27 5:26 ` qemudev
2024-02-27 5:46 ` |SUCCESS| pw137311 " checkpatch
2024-02-27 6:45 ` 0-day Robot [this message]
2024-02-28 2:10 ` |SUCCESS| pw137295-137311 [PATCH] [v6,23/23] devtools: forbid new us dpdklab
2024-02-28 2:17 ` dpdklab
2024-02-29 6:03 ` dpdklab
2024-02-29 6:06 ` dpdklab
2024-02-29 6:09 ` dpdklab
2024-02-29 6:10 ` dpdklab
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=20240227064531.325618-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=roretzla@linux.microsoft.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).