From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com, robot@bytheb.org
Subject: |FAILURE| pw126992 [PATCH v5 3/3] telemetry: use standard logging
Date: Thu, 18 May 2023 19:19:52 -0400 [thread overview]
Message-ID: <20230518231952.2940472-1-robot@bytheb.org> (raw)
In-Reply-To: <20230518124949.879834-4-bruce.richardson@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/126992/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5014213773
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
####################################################################################
17 Removed functions:
[D] 'function int rte_log(uint32_t, uint32_t, const char*, ...)' {rte_log@@DPDK_23}
[D] 'function bool rte_log_can_log(uint32_t, uint32_t)' {rte_log_can_log@@DPDK_23}
[D] 'function int rte_log_cur_msg_loglevel()' {rte_log_cur_msg_loglevel@@DPDK_23}
[D] 'function int rte_log_cur_msg_logtype()' {rte_log_cur_msg_logtype@@DPDK_23}
[D] 'function void rte_log_dump(FILE*)' {rte_log_dump@@DPDK_23}
[D] 'function uint32_t rte_log_get_global_level()' {rte_log_get_global_level@@DPDK_23}
[D] 'function int rte_log_get_level(uint32_t)' {rte_log_get_level@@DPDK_23}
[D] 'function FILE* rte_log_get_stream()' {rte_log_get_stream@@DPDK_23}
[D] 'function void rte_log_list_types(FILE*, const char*)' {rte_log_list_types@@DPDK_23}
[D] 'function int rte_log_register(const char*)' {rte_log_register@@DPDK_23}
[D] 'function int rte_log_register_type_and_pick_level(const char*, uint32_t)' {rte_log_register_type_and_pick_level@@DPDK_23}
[D] 'function void rte_log_set_global_level(uint32_t)' {rte_log_set_global_level@@DPDK_23}
[D] 'function int rte_log_set_level(uint32_t, uint32_t)' {rte_log_set_level@@DPDK_23}
[D] 'function int rte_log_set_level_pattern(const char*, uint32_t)' {rte_log_set_level_pattern@@DPDK_23}
[D] 'function int rte_log_set_level_regexp(const char*, uint32_t)' {rte_log_set_level_regexp@@DPDK_23}
[D] 'function int rte_openlog_stream(FILE*)' {rte_openlog_stream@@DPDK_23}
[D] 'function int rte_vlog(uint32_t, uint32_t, const char*, __va_list_tag*)' {rte_vlog@@DPDK_23}
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).
ABIDIFF_ABI_INCOMPATIBLE_CHANGE, this change breaks the ABI.
##[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-05-18 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230518124949.879834-4-bruce.richardson@intel.com>
2023-05-18 12:38 ` |SUCCESS| pw126990-126992 " qemudev
2023-05-18 12:42 ` qemudev
2023-05-18 12:51 ` |SUCCESS| pw126992 " checkpatch
2023-05-18 23:19 ` 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=20230518231952.2940472-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=bruce.richardson@intel.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).