From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] a561d44985d3900d505abb6dd23fa861c5e9eab7
Date: Sat, 13 Aug 2022 05:57:42 +0000 (UTC) [thread overview]
Message-ID: <20220813055742.58D3E6043F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2886 bytes --]
_Testing issues_
Branch: tags/v21.11
a561d44985d3900d505abb6dd23fa861c5e9eab7 --> testing fail
Test environment and result as below:
+-----------------------------+----------+
| Environment | abi_test |
+=============================+==========+
| Ubuntu 20.04 ARM GCC Native | PASS |
+-----------------------------+----------+
| RHEL 7 | FAIL |
+-----------------------------+----------+
| openSUSE Leap 15 | FAIL |
+-----------------------------+----------+
| Fedora 34 clang | FAIL |
+-----------------------------+----------+
| RHEL8 | FAIL |
+-----------------------------+----------+
==== 20 line log output for RHEL8 (abi_test): ====
in pointed to type 'struct rte_mbuf' at rte_mbuf_core.h:578:1:
type size hasn't changed
1 data member changes (4 filtered):
type of 'anonymous data member union {uint32_t packet_type; struct {uint8_t l2_type; uint8_t l3_type; uint8_t l4_type; uint8_t tun_type; union {uint8_t inner_esp_next_proto; struct {uint8_t inner_l2_type; uint8_t inner_l3_type;};}; uint8_t inner_l4_type;};}' changed:
type size hasn't changed
1 data member changes (1 filtered):
type of 'anonymous data member struct {uint8_t l2_type; uint8_t l3_type; uint8_t l4_type; uint8_t tun_type; union {uint8_t inner_esp_next_proto; struct {uint8_t inner_l2_type; uint8_t inner_l3_type;};}; uint8_t inner_l4_type;}' changed:
type size hasn't changed
3 data member changes (1 filtered):
'uint8_t inner_l4_type' offset changed from 0 to 24 (in bits) (by +24 bits)
'uint8_t l4_type' offset changed from 0 to 8 (in bits) (by +8 bits)
'uint8_t tun_type' offset changed from 4 to 12 (in bits) (by +8 bits)
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_mbuf.dump build_install/dump/librte_mbuf.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
==== End log output ====
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20997/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-08-13 5:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 5:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-13 0:24 dpdklab
2022-09-12 23:33 dpdklab
2022-09-12 22:22 dpdklab
2022-09-12 21:33 dpdklab
2022-08-17 6:08 dpdklab
2022-08-16 6:09 dpdklab
2022-08-15 5:36 dpdklab
2022-08-14 5:46 dpdklab
2022-08-12 6:28 dpdklab
2022-08-12 3:17 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=20220813055742.58D3E6043F@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).