automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw150426-150428 [PATCH] [v1,3/3] baseband/acc: add interna
Date: Thu, 23 Jan 2025 14:52:37 -0800 (PST)	[thread overview]
Message-ID: <6792c835.050a0220.34a171.2b89SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250123202807.2089618-4-nicolas.chautru@intel.com>

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

_Testing issues_

Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Thursday, January 23 2025 20:28:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:07e3bebf3c93750c52ed9be87edd212fbc22da0a

150426-150428 --> testing issues

Upstream job id: Generic-DPDK-Compile-ABI#113409

Test environment and result as below:

+-------------------+----------+
|    Environment    | abi_test |
+===================+==========+
| CentOS Stream 9   | FAIL     |
+-------------------+----------+
| Fedora 40 (Clang) | FAIL     |
+-------------------+----------+
| Debian 12         | FAIL     |
+-------------------+----------+
| Fedora 41 (Clang) | FAIL     |
+-------------------+----------+
| Fedora 40         | FAIL     |
+-------------------+----------+
| RHEL8             | FAIL     |
+-------------------+----------+
| openSUSE Leap 15  | FAIL     |
+-------------------+----------+
| RHEL9             | FAIL     |
+-------------------+----------+
| Fedora 41         | FAIL     |
+-------------------+----------+
| Ubuntu 22.04      | FAIL     |
+-------------------+----------+
| Ubuntu 24.04      | FAIL     |
+-------------------+----------+

==== 20 line log output for Ubuntu 24.04 (abi_test): ====
Variables changes summary: 0 Removed, 0 Changed, 0 Added (2 filtered out) variables

Functions changes summary: 0 Removed, 1 Changed (9 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 bool __rte_graph_mcore_dispatch_sched_node_enqueue(rte_node*, rte_graph_rq_head*)' at rte_graph_model_mcore_dispatch.c:117:1 has some indirect sub-type changes:
parameter 1 of type 'rte_node*' has sub-type changes:
in pointed to type 'struct rte_node' at rte_graph_worker_common.h:92:1:
type size changed from 3072 to 2560 (in bits)
3 data member changes (1 filtered):
type of 'anonymous data member union {struct {unsigned int lcore_id; uint64_t total_sched_objs; uint64_t total_sched_fail;} dispatch;}' changed:
type size changed from 512 to 192 (in bits)
and offset changed from 1536 to 1344 (in bits) (by -192 bits)
'rte_graph_off_t xstat_off' offset changed from 2048 to 1536 (in bits) (by -512 bits)
anonymous data member 'struct {union {uint8_t ctx[16]; struct {void* ctx_ptr; void* ctx_ptr2;};}; uint16_t size; uint16_t idx; rte_graph_off_t off; uint64_t total_cycles; uint64_t total_calls; uint64_t total_objs; union {void** objs; uint64_t objs_u64;}; union {rte_node_process_t process; uint64_t process_u64;}; rte_node* nodes[];}' offset changed from 2560 to 2048 (in bits) (by -512 bits)

Error: ABI issue reported for abidiff --suppr /home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-ABI@3/dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 build_install/usr/local/include reference/usr/local/lib/x86_64-linux-gnu/librte_graph.so.25.0 build_install/usr/local/lib/x86_64-linux-gnu/librte_graph.so.25.0
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
==== End log output ====

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

openSUSE Leap 15
	Kernel: Depends on container host
	Compiler: gcc (SUSE Linux) 7.5.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Fedora 41
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-01-23 22:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250123202807.2089618-4-nicolas.chautru@intel.com>
2025-01-23 20:07 ` |SUCCESS| pw150426-150428 [PATCH v1 3/3] baseband/acc: add internal logging qemudev
2025-01-23 20:11 ` qemudev
2025-01-23 20:40 ` |SUCCESS| pw150428 " checkpatch
2025-01-23 21:18 ` |PENDING| pw150426-150428 [PATCH] [v1,3/3] baseband/acc: add interna dpdklab
2025-01-23 21:21 ` dpdklab
2025-01-23 21:21 ` dpdklab
2025-01-23 21:22 ` dpdklab
2025-01-23 21:24 ` |SUCCESS| " dpdklab
2025-01-23 21:28 ` |PENDING| " dpdklab
2025-01-23 21:33 ` |SUCCESS| " dpdklab
2025-01-23 21:36 ` dpdklab
2025-01-23 21:36 ` |WARNING| " dpdklab
2025-01-23 21:38 ` |SUCCESS| " dpdklab
2025-01-23 21:44 ` |FAILURE| pw150428 [PATCH v1 3/3] baseband/acc: add internal logging 0-day Robot
2025-01-23 21:48 ` |SUCCESS| pw150426-150428 [PATCH] [v1,3/3] baseband/acc: add interna dpdklab
2025-01-23 21:51 ` dpdklab
2025-01-23 22:07 ` dpdklab
2025-01-23 22:09 ` dpdklab
2025-01-23 22:51 ` |WARNING| " dpdklab
2025-01-23 22:52 ` dpdklab [this message]
2025-01-23 22:56 ` |SUCCESS| " dpdklab

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=6792c835.050a0220.34a171.2b89SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).