From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Chaoyong He <chaoyong.he@corigine.com>,
dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Chaoyong He <chaoyong.he@corigine.com>
Subject: |WARNING| pw126723 [PATCH] app/pdump: make dpdk-pdump can run multiple simultaneously
Date: Sat, 06 May 2023 02:55:38 -0700 (PDT) [thread overview]
Message-ID: <6456241a.050a0220.a565f.67b3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/126723
_Testing issues_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Saturday, May 06 2023 08:52:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61
126723 --> testing fail
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| RHEL 7 | FAIL |
+-----------------+----------+
| Ubuntu 22.04 | FAIL |
+-----------------+----------+
| CentOS Stream 9 | FAIL |
+-----------------+----------+
| Debian Buster | FAIL |
+-----------------+----------+
==== 20 line log output for Debian Buster (abi_test): ====
'uint32_t nb_mem_chunks' offset changed from 1024 to 1280 (in bits) (by +256 bits)
'rte_mempool_memhdr_list mem_list' offset changed from 1088 to 1344 (in bits) (by +256 bits)
Error: ABI issue reported for abidiff --suppr /home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-ABI/dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 build_install/usr/local/include reference/usr/local/lib/x86_64-linux-gnu/librte_mempool.so.23.0 build_install/usr/local/lib/x86_64-linux-gnu/librte_mempool.so.23.2
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed (1 filtered out), 0 Changed (281 filtered out), 0 Added (42 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
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 (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (200 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
==== End log output ====
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26176/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-06 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 9:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-06 10:17 dpdklab
2023-05-06 10:15 dpdklab
2023-05-06 10:05 dpdklab
2023-05-06 10:04 dpdklab
2023-05-06 10:02 dpdklab
2023-05-06 10:00 dpdklab
2023-05-06 9:58 dpdklab
2023-05-06 9:57 dpdklab
2023-05-06 9:57 dpdklab
2023-05-06 9:55 dpdklab
2023-05-06 9:53 dpdklab
2023-05-06 9:48 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=6456241a.050a0220.a565f.67b3SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chaoyong.he@corigine.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).