automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw122429-122431 [PATCH] [v4, 3/3] telemetry: use standard logging
Date: Sat, 21 Jan 2023 20:57:58 +0000 (UTC)	[thread overview]
Message-ID: <20230121205758.170BE601CE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 3914 bytes --]

Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/122431

_Testing issues_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, January 20 2023 18:21:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a211079a92e962bbd0ec81e425a6ffc32890e67

122429-122431 --> testing fail

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| RHEL 7           | FAIL     |
+------------------+----------+
| Ubuntu 22.04     | FAIL     |
+------------------+----------+
| Debian Bullseye  | FAIL     |
+------------------+----------+
| CentOS Stream 9  | FAIL     |
+------------------+----------+
| CentOS Stream 8  | FAIL     |
+------------------+----------+
| openSUSE Leap 15 | FAIL     |
+------------------+----------+
| Debian Buster    | FAIL     |
+------------------+----------+
| RHEL8            | FAIL     |
+------------------+----------+
| Ubuntu 20.04     | FAIL     |
+------------------+----------+

==== 20 line log output for Ubuntu 20.04 (abi_test): ====
[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 dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/include --headers-dir2 build_install/include reference/dump/librte_eal.dump build_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.
==== 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

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25054/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

                 reply	other threads:[~2023-01-21 20:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230121205758.170BE601CE@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.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).