From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: Sivaprasad.Tummala@amd.com, robot@bytheb.org
Subject: |FAILURE| pw125875 [PATCH v1] power: amd power monitor support
Date: Mon, 10 Apr 2023 07:38:54 -0400 [thread overview]
Message-ID: <20230410113854.821066-1-robot@bytheb.org> (raw)
In-Reply-To: <20230410102149.198389-1-Sivaprasad.Tummala@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/125875/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4656736939
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
type of 'const rte_cpu_flag_t* cpu_flag_reqs' changed:
in pointed to type 'const rte_cpu_flag_t':
in unqualified underlying type 'enum rte_cpu_flag_t' at rte_cpuflags.h:12:1:
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
Functions changes summary: 0 Removed, 1 Changed (2 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
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/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/x86_64-linux-gnu/librte_eal.so.23.1 install/usr/local/lib/x86_64-linux-gnu/librte_eal.so.23.2
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-04-10 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230410102149.198389-1-Sivaprasad.Tummala@amd.com>
2023-04-10 10:12 ` |SUCCESS| " qemudev
2023-04-10 10:16 ` qemudev
2023-04-10 10:24 ` checkpatch
2023-04-10 11:38 ` 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=20230410113854.821066-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=Sivaprasad.Tummala@amd.com \
--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).