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,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw136622 [PATCH] [v2] mbuf: replace GCC marker extension w
Date: Mon, 12 Feb 2024 23:37:07 -0800 (PST)	[thread overview]
Message-ID: <65cb1c23.810a0220.33bcd.c969SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 13 2024 06:45:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:547f294357690ab8501f120457a82919b1217517

136622 --> testing fail

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| Debian Buster   | FAIL     |
+-----------------+----------+
| CentOS Stream 9 | FAIL     |
+-----------------+----------+
| Fedora 37       | FAIL     |
+-----------------+----------+

==== 20 line log output for Fedora 37 (abi_test): ====
in pointed to type 'struct rte_crypto_op' at rte_crypto.h:91:1:
type size hasn't changed
1 data member change:
type of 'anonymous data member union {rte_crypto_sym_op sym[]; rte_crypto_asym_op asym[];}' changed:
type size hasn't changed
1 data member change:
type of 'rte_crypto_sym_op sym[]' changed:
array element type 'struct rte_crypto_sym_op' changed:
type size hasn't changed
1 data member changes (1 filtered):
type of 'rte_mbuf* m_src' changed:
in pointed to type 'struct rte_mbuf' at rte_mbuf_core.h:466:1:
type size hasn't changed
2 data member deletions:
'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;};}', at offset 256 (in bits)
'union {union {uint32_t rss; struct {union {struct {uint16_t hash; uint16_t id;}; uint32_t lo;}; uint32_t hi;} fdir; rte_mbuf_sched sched; struct {uint32_t reserved1; uint16_t reserved2; uint16_t txq;} txadapter; uint32_t usr;} hash;}', at offset 352 (in bits)
type size hasn't changed

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

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

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

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-13  7:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  7:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-13  8:02 dpdklab
2024-02-13  7:49 dpdklab
2024-02-13  7:47 dpdklab
2024-02-13  7:45 dpdklab
2024-02-13  7:41 dpdklab
2024-02-13  7:41 dpdklab
2024-02-13  7:38 dpdklab
2024-02-13  7:36 dpdklab
2024-02-13  7:34 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=65cb1c23.810a0220.33bcd.c969SMTPIN_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).