From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw137407-137409 [PATCH] [v3,6/6] table: replace zero lengt
Date: Wed, 28 Feb 2024 00:24:21 -0800 (PST) [thread overview]
Message-ID: <65deedb5.050a0220.3ae5a.644eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709078215-20292-7-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/137409
_Testing issues_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 27 2024 23:56:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137407-137409 --> testing fail
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | FAIL |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Fedora 38 | FAIL |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 37 | FAIL |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian 12 (arm) | PASS |
+------------------+----------+
| Ubuntu 22.04 | FAIL |
+------------------+----------+
==== 20 line log output for Ubuntu 22.04 (abi_test): ====
1 data member change:
type of 'rte_cryptodev_qpdata qp' changed:
type size hasn't changed
1 data member changes (1 filtered):
type of 'rte_cryptodev_cb_rcu* enq_cb' changed:
in pointed to type 'struct rte_cryptodev_cb_rcu' at rte_cryptodev.h:989:1:
type size hasn't changed
1 data member change:
type of 'rte_rcu_qsbr* qsbr' changed:
in pointed to type 'struct rte_rcu_qsbr' at rte_rcu_qsbr.h:94:1:
type size hasn't changed
1 data member change:
'rte_rcu_qsbr_cnt qsbr_cnt[]' has *some* difference - please report as a bug
type size hasn't changed
Error: ABI issue reported for abidiff --suppr /home-local/jenkins-local/jenkins-agent/workspace/Generic-DPDK-Compile-ABI@2/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_cryptodev.so.24.0 build_install/usr/local/lib/x86_64-linux-gnu/librte_cryptodev.so.24.1
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed, 0 Changed, 0 Added (2 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
==== End log output ====
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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29306/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-28 8:24 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709078215-20292-7-git-send-email-roretzla@linux.microsoft.com>
2024-02-27 23:34 ` |SUCCESS| pw137407-137409 [PATCH v3 6/6] table: replace zero length array with flex array qemudev
2024-02-27 23:38 ` qemudev
2024-02-27 23:58 ` |SUCCESS| pw137409 " checkpatch
2024-02-28 0:45 ` |FAILURE| " 0-day Robot
2024-02-28 8:07 ` |SUCCESS| pw137407-137409 [PATCH] [v3,6/6] table: replace zero lengt dpdklab
2024-02-28 8:08 ` dpdklab
2024-02-28 8:10 ` |WARNING| " dpdklab
2024-02-28 8:12 ` |SUCCESS| " dpdklab
2024-02-28 8:13 ` dpdklab
2024-02-28 8:14 ` dpdklab
2024-02-28 8:24 ` dpdklab [this message]
2024-02-28 8:25 ` |WARNING| " dpdklab
2024-02-28 8:26 ` dpdklab
2024-02-28 8:26 ` |SUCCESS| " dpdklab
2024-02-28 8:26 ` |WARNING| " dpdklab
2024-02-28 8:26 ` dpdklab
2024-02-28 8:26 ` |SUCCESS| " dpdklab
2024-02-28 8:29 ` |WARNING| " dpdklab
2024-02-28 8:35 ` |SUCCESS| " dpdklab
2024-02-28 8:36 ` |WARNING| " dpdklab
2024-02-28 8:38 ` dpdklab
2024-02-28 8:39 ` |SUCCESS| " dpdklab
2024-02-28 8:39 ` dpdklab
2024-02-28 8:40 ` dpdklab
2024-02-28 8:44 ` dpdklab
2024-02-28 8:44 ` dpdklab
2024-02-28 8:44 ` dpdklab
2024-02-28 8:45 ` dpdklab
2024-02-28 8:45 ` dpdklab
2024-02-28 8:45 ` dpdklab
2024-02-28 8:47 ` dpdklab
2024-02-28 8:47 ` dpdklab
2024-02-28 8:47 ` dpdklab
2024-02-28 8:48 ` dpdklab
2024-02-28 8:48 ` dpdklab
2024-02-28 8:48 ` dpdklab
2024-02-28 8:48 ` dpdklab
2024-02-28 8:49 ` dpdklab
2024-02-28 8:50 ` dpdklab
2024-02-28 8:51 ` dpdklab
2024-02-28 8:51 ` dpdklab
2024-02-28 8:52 ` dpdklab
2024-02-28 8:53 ` dpdklab
2024-02-28 8:54 ` dpdklab
2024-02-28 8:57 ` dpdklab
2024-02-28 8:58 ` dpdklab
2024-02-28 9:00 ` dpdklab
2024-02-28 9:03 ` dpdklab
2024-02-28 9:05 ` dpdklab
2024-02-28 9:07 ` dpdklab
2024-02-28 9:12 ` dpdklab
2024-02-28 9:15 ` dpdklab
2024-02-28 9:19 ` dpdklab
2024-02-28 9:22 ` dpdklab
2024-02-28 9:23 ` dpdklab
2024-02-28 9:25 ` dpdklab
2024-02-28 9:26 ` dpdklab
2024-02-28 9:27 ` dpdklab
2024-02-28 9:32 ` dpdklab
2024-02-28 9:54 ` dpdklab
2024-02-28 11:45 ` dpdklab
2024-02-28 15:59 ` dpdklab
2024-02-28 16:59 ` dpdklab
2024-02-28 17:06 ` dpdklab
2024-02-29 5:17 ` dpdklab
2024-02-29 19:54 ` dpdklab
2024-02-29 19:57 ` dpdklab
2024-02-29 19:59 ` dpdklab
2024-02-29 20:02 ` dpdklab
2024-03-01 5:38 ` dpdklab
2024-03-01 6:00 ` dpdklab
2024-03-01 6:35 ` 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=65deedb5.050a0220.3ae5a.644eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=roretzla@linux.microsoft.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).