From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: Sivaprasad.Tummala@amd.com, robot@bytheb.org
Subject: |FAILURE| pw125868 [PATCH] power: amd power monitor support
Date: Mon, 10 Apr 2023 01:58:52 -0400 [thread overview]
Message-ID: <20230410055852.605926-1-robot@bytheb.org> (raw)
In-Reply-To: <20230410043558.5515-1-Sivaprasad.Tummala@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/125868/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4654630597
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
####################################################################################
'rte_cpu_flag_t::RTE_CPUFLAG_EM64T' from value '85' to '86' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_INVTSC' from value '86' to '87' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512DQ' from value '87' to '88' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512IFMA' from value '88' to '89' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512CD' from value '89' to '90' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512BW' from value '90' to '91' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512VL' from value '91' to '92' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512VBMI' from value '92' to '93' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512VBMI2' from value '93' to '94' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_GFNI' from value '94' to '95' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_VAES' from value '95' to '96' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_VPCLMULQDQ' from value '96' to '97' at rte_cpuflags.h:12:1
'rte_cpu_flag_t::RTE_CPUFLAG_AVX512VNNI' from value '97' to '98' at rte_cpuflags.h:12:1
'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/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 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230410043558.5515-1-Sivaprasad.Tummala@amd.com>
2023-04-10 4:27 ` |SUCCESS| " qemudev
2023-04-10 4:31 ` qemudev
2023-04-10 4:38 ` checkpatch
2023-04-10 5:58 ` 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=20230410055852.605926-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).