From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: vipin.varghese@amd.com, robot@bytheb.org
Subject: |FAILURE| pw134886 [PATCH] cfgfile: increase value length
Date: Wed, 6 Dec 2023 07:25:44 -0500 [thread overview]
Message-ID: <20231206122544.316397-1-robot@bytheb.org> (raw)
In-Reply-To: <20231206112952.1588-1-vipin.varghese@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/134886/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7114077738
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
+ devtools/check-abi.sh reference install
Functions changes summary: 0 Removed, 0 Changed, 0 Added (3 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed, 1 Changed (16 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
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_cfgfile.so.24.0 install/usr/local/lib/librte_cfgfile.so.24.1
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
1 function with some indirect sub-type change:
[C] 'function int rte_cfgfile_section_entries(rte_cfgfile*, const char*, rte_cfgfile_entry*, int)' at rte_cfgfile.c:522:1 has some indirect sub-type changes:
parameter 3 of type 'rte_cfgfile_entry*' has sub-type changes:
in pointed to type 'struct rte_cfgfile_entry' at rte_cfgfile.h:34:1:
type size changed from 2560 to 16896 (in bits)
1 data member change:
type of 'char value[256]' changed:
type name changed from 'char[256]' to 'char[2048]'
array type size changed from 2048 to 16384
array type subrange 1 changed length from 256 to 2048
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-12-06 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231206112952.1588-1-vipin.varghese@amd.com>
2023-12-06 11:11 ` |SUCCESS| " qemudev
2023-12-06 11:16 ` qemudev
2023-12-06 11:32 ` checkpatch
2023-12-06 12:25 ` 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=20231206122544.316397-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=vipin.varghese@amd.com \
/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).