From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: haijie1@huawei.com, robot@bytheb.org
Subject: |FAILURE| pw126799 [PATCH v6 3/3] ring: add telemetry cmd for ring info
Date: Tue, 9 May 2023 06:59:54 -0400 [thread overview]
Message-ID: <20230509105954.1192418-1-robot@bytheb.org> (raw)
In-Reply-To: <20230509092459.20140-4-haijie1@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/126799/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4924691294
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
1 function with some indirect sub-type change:
[C] 'function rte_event_ring* rte_event_ring_create(const char*, unsigned int, int, unsigned int)' at rte_event_ring.c:26:1 has some indirect sub-type changes:
return type changed:
in pointed to type 'struct rte_event_ring' at rte_event_ring.h:37:1:
type size hasn't changed
1 data member change:
type of 'rte_ring r' changed:
type size hasn't changed
1 data member change:
type of 'int flags' changed:
entity changed from 'int' to compatible type 'typedef uint32_t' at stdint-uintn.h:26:1
type name changed from 'int' to 'unsigned int'
type size hasn't changed
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/x86_64-linux-gnu/librte_eventdev.so.23.1 install/usr/local/lib/x86_64-linux-gnu/librte_eventdev.so.23.2
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed, 0 Changed, 0 Added (4 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (7 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+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2023-05-09 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230509092459.20140-4-haijie1@huawei.com>
2023-05-09 9:28 ` |SUCCESS| " checkpatch
2023-05-09 10:59 ` 0-day Robot [this message]
2023-05-10 1:39 ` |SUCCESS| pw126797-126799 " qemudev
2023-05-10 1:39 ` qemudev
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=20230509105954.1192418-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=haijie1@huawei.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).