automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com, robot@bytheb.org
Subject: |FAILURE| pw122051 [PATCH v3 3/3] telemetry: use standard logging
Date: Fri, 13 Jan 2023 17:00:05 -0500	[thread overview]
Message-ID: <20230113220005.3994179-1-robot@bytheb.org> (raw)
In-Reply-To: <20230113203656.1864072-4-bruce.richardson@intel.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/122051/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/3914878473
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
  [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 devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/dump/librte_eal.dump install/dump/librte_eal.dump'


ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
ABIDIFF_ABI_INCOMPATIBLE_CHANGE, this change breaks the ABI.
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 (4 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

      parent reply	other threads:[~2023-01-13 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230113203656.1864072-4-bruce.richardson@intel.com>
2023-01-13 20:29 ` |SUCCESS| pw122049-122051 " qemudev
2023-01-13 20:33 ` qemudev
2023-01-13 20:38 ` |SUCCESS| pw122051 " checkpatch
2023-01-13 22:00 ` 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=20230113220005.3994179-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).