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| pw125875 [PATCH] [v1] power: amd power monitor support
Date: Mon, 10 Apr 2023 11:17:39 +0000 (UTC) [thread overview]
Message-ID: <20230410111739.28C6A60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/125875
_Testing issues_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, April 10 2023 10:21:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125875 --> testing fail
Test environment and result as below:
+--------------+----------+
| Environment | abi_test |
+==============+==========+
| RHEL 7 | FAIL |
+--------------+----------+
| Ubuntu 22.04 | FAIL |
+--------------+----------+
==== 20 line log output for Ubuntu 22.04 (abi_test): ====
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed (1 filtered out), 1 Changed (2 filtered out), 0 Added (3 filtered out) functions
Variables changes summary: 0 Removed (15 filtered out), 0 Changed, 0 Added (1 filtered out) variables
1 function with some indirect sub-type change:
[C] 'function int rte_cpu_get_flag_enabled(rte_cpu_flag_t)' at rte_cpuflags.c:148:1 has some indirect sub-type changes:
parameter 1 of type 'enum rte_cpu_flag_t' has sub-type changes:
type size hasn't changed
1 enumerator insertion:
'rte_cpu_flag_t::RTE_CPUFLAG_MONITORX' value '105'
1 enumerator change:
'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, 0 Changed, 0 Added (1 filtered out) function
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25946/
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 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 11:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 11:25 dpdklab
2023-04-10 11:25 dpdklab
2023-04-10 11:23 dpdklab
2023-04-10 11:22 dpdklab
2023-04-10 11:22 dpdklab
2023-04-10 11:21 dpdklab
2023-04-10 11:20 dpdklab
2023-04-10 11:20 dpdklab
2023-04-10 11:19 dpdklab
2023-04-10 11:17 dpdklab
2023-04-10 11:14 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=20230410111739.28C6A60095@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).