From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>,
dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Subject: |WARNING| pw126156-126158 [PATCH] [v3, 4/4] power: amd power monitor support
Date: Mon, 17 Apr 2023 09:16:48 +0000 (UTC) [thread overview]
Message-ID: <20230417091648.7B50A60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/126158
_Testing issues_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, April 17 2023 04:34:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126156-126158 --> testing fail
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| RHEL 7 | FAIL |
+-----------------+----------+
| Ubuntu 22.04 | FAIL |
+-----------------+----------+
| CentOS Stream 9 | FAIL |
+-----------------+----------+
| Debian Bullseye | FAIL |
+-----------------+----------+
==== 20 line log output for Debian Bullseye (abi_test): ====
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed (6 filtered out), 0 Changed, 0 Added (62 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed (14 filtered out), 0 Changed, 0 Added variables
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, 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 ====
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 Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26012/
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-17 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-17 9:30 dpdklab
2023-04-17 9:30 dpdklab
2023-04-17 9:26 dpdklab
2023-04-17 9:25 dpdklab
2023-04-17 9:22 dpdklab
2023-04-17 9:18 dpdklab
2023-04-17 9:16 dpdklab
2023-04-17 9:15 dpdklab
2023-04-17 9:15 dpdklab
2023-04-17 9:11 dpdklab
2023-04-17 9:11 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=20230417091648.7B50A60092@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).