From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw136940 [RFC] eal: increase maximum number of file descriptors in MP message
Date: Tue, 20 Feb 2024 19:04:40 -0500 [thread overview]
Message-ID: <20240221000440.1025344-1-robot@bytheb.org> (raw)
In-Reply-To: <20240220230941.293399-2-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/136940/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/7981420145
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
####################################################################################
parameter 1 of type 'const rte_mp_msg*' has sub-type changes:
in pointed to type 'const rte_mp_msg':
in unqualified underlying type 'struct rte_mp_msg' at rte_eal.h:163:1:
type size changed from 2880 to 10720 (in bits)
1 data member change:
type of 'int fds[8]' changed:
type name changed from 'int[8]' to 'int[253]'
array type size changed from 256 to 8096
array type subrange 1 changed length from 8 to 253
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_eal.so.24.0 install/usr/local/lib/librte_eal.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 (89 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed (1 filtered out), 0 Changed (31 filtered out), 0 Added (5 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (39 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added (2 filtered out) variables
Functions changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) function
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-----------------------------
prev parent reply other threads:[~2024-02-21 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240220230941.293399-2-stephen@networkplumber.org>
2024-02-20 22:47 ` |SUCCESS| " qemudev
2024-02-20 22:51 ` qemudev
2024-02-20 23:11 ` checkpatch
2024-02-21 0:04 ` 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=20240221000440.1025344-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=stephen@networkplumber.org \
--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).