From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Subject: |WARNING| pw125868 [PATCH] power: amd power monitor support
Date: Mon, 10 Apr 2023 05:59:17 +0000 (UTC) [thread overview]
Message-ID: <20230410055917.B782360095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/125868
_Testing issues_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, April 10 2023 04:35:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125868 --> testing fail
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | FAIL |
+------------------+----------+
| Debian Bullseye | FAIL |
+------------------+----------+
| openSUSE Leap 15 | FAIL |
+------------------+----------+
| Debian Buster | FAIL |
+------------------+----------+
| CentOS Stream 8 | FAIL |
+------------------+----------+
==== 20 line log output for CentOS Stream 8 (abi_test): ====
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512BITALG' from value '98' to '99' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512VPOPCNTDQ' from value '99' to '100' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_CLDEMOTE' from value '100' to '101' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_MOVDIRI' from value '101' to '102' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_MOVDIR64B' from value '102' to '103' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512VP2INTERSECT' from value '103' to '104' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_WAITPKG' from value '104' to '105' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_NUMFLAGS' from value '105' to '106' at rte_cpuflags.h:12:1
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/lib64/librte_eal.so.23.0 build_install/usr/local/lib64/librte_eal.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 (2 filtered out), 0 Added (1 filtered out) functions
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
==== End log output ====
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25943/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-10 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 5:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 6:17 dpdklab
2023-04-10 6:17 dpdklab
2023-04-10 6:15 dpdklab
2023-04-10 6:14 dpdklab
2023-04-10 6:03 dpdklab
2023-04-10 5:56 dpdklab
2023-04-10 5:52 dpdklab
2023-04-10 5:51 dpdklab
2023-04-10 5:51 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=20230410055917.B782360095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=Sivaprasad.Tummala@amd.com \
--cc=david.marchand@redhat.com \
--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).