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| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar
Date: Wed, 27 Mar 2024 13:52:28 -0700 (PDT)	[thread overview]
Message-ID: <6604870c.050a0220.1f7ed.88ccSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1711569406-7750-5-git-send-email-roretzla@linux.microsoft.com>

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

_Testing issues_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 27 2024 19:56:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ded4d4765171b88470e59307f10625e942f22fca

138873-138875 --> testing fail

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| openSUSE Leap 15 | FAIL     |
+------------------+----------+
| Fedora 38        | FAIL     |
+------------------+----------+
| CentOS Stream 9  | FAIL     |
+------------------+----------+
| Ubuntu 22.04     | FAIL     |
+------------------+----------+
| Fedora 37        | FAIL     |
+------------------+----------+
| Debian Bullseye  | FAIL     |
+------------------+----------+
| CentOS Stream 8  | FAIL     |
+------------------+----------+
| Fedora 39        | FAIL     |
+------------------+----------+
| RHEL8            | FAIL     |
+------------------+----------+
| Debian 11 (arm)  | FAIL     |
+------------------+----------+

==== 20 line log output for Debian 11 (arm) (abi_test): ====
[C] 'function const rte_eth_rxtx_callback* rte_eth_add_first_rx_callback(uint16_t, uint16_t, rte_rx_callback_fn, void*)' at rte_ethdev.c:5789:1 has some indirect sub-type changes:
parameter 3 of type 'typedef rte_rx_callback_fn' has sub-type changes:
underlying type 'typedef uint16_t (typedef uint16_t, typedef uint16_t, rte_mbuf**, typedef uint16_t, typedef uint16_t, void*)*' changed:
in pointed to type 'function type typedef uint16_t (typedef uint16_t, typedef uint16_t, rte_mbuf**, typedef uint16_t, typedef uint16_t, void*)':
parameter 3 of type 'rte_mbuf**' has sub-type changes:
in pointed to type 'rte_mbuf*':
in pointed to type 'struct rte_mbuf' at rte_mbuf_core.h:467:1:
type size hasn't changed
4 data member deletions:
'RTE_MARKER cacheline0', at offset 0 (in bits) at rte_mbuf_core.h:467:1
'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)
'RTE_MARKER cacheline1', at offset 512 (in bits) at rte_mbuf_core.h:598:1
no data member change (1 filtered);

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/lib/x86_64-linux-gnu/librte_ethdev.so.24.0 build_install/usr/local/lib/x86_64-linux-gnu/librte_ethdev.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 ====

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

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

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-27 20:52 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1711569406-7750-5-git-send-email-roretzla@linux.microsoft.com>
2024-03-27 19:35 ` |SUCCESS| pw138873-138875 [PATCH v8 4/4] cryptodev: remove rte marker fields qemudev
2024-03-27 19:39 ` qemudev
2024-03-27 19:57 ` |SUCCESS| pw138875 " checkpatch
2024-03-27 20:35 ` |SUCCESS| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:37 ` dpdklab
2024-03-27 20:37 ` dpdklab
2024-03-27 20:38 ` dpdklab
2024-03-27 20:40 ` |WARNING| " dpdklab
2024-03-27 20:42 ` dpdklab
2024-03-27 20:43 ` |SUCCESS| " dpdklab
2024-03-27 20:44 ` dpdklab
2024-03-27 20:44 ` |WARNING| " dpdklab
2024-03-27 20:44 ` dpdklab
2024-03-27 20:45 ` |FAILURE| pw138875 [PATCH v8 4/4] cryptodev: remove rte marker fields 0-day Robot
2024-03-27 20:45 ` |SUCCESS| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar dpdklab
2024-03-27 20:46 ` |WARNING| " dpdklab
2024-03-27 20:47 ` dpdklab
2024-03-27 20:48 ` dpdklab
2024-03-27 20:49 ` |SUCCESS| " dpdklab
2024-03-27 20:52 ` dpdklab [this message]
2024-03-27 20:53 ` |WARNING| " dpdklab
2024-03-27 20:56 ` |SUCCESS| " dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:59 ` dpdklab
2024-03-27 21:00 ` dpdklab
2024-03-27 21:01 ` dpdklab
2024-03-27 21:01 ` dpdklab
2024-03-27 21:03 ` dpdklab
2024-03-27 21:05 ` dpdklab
2024-03-27 21:06 ` dpdklab
2024-03-27 21:06 ` dpdklab
2024-03-27 21:08 ` dpdklab
2024-03-27 21:09 ` dpdklab
2024-03-27 21:09 ` dpdklab
2024-03-27 21:10 ` dpdklab
2024-03-27 21:12 ` dpdklab
2024-03-27 21:12 ` dpdklab
2024-03-27 21:13 ` dpdklab
2024-03-27 21:13 ` dpdklab
2024-03-27 21:16 ` dpdklab
2024-03-27 21:16 ` dpdklab
2024-03-27 21:22 ` dpdklab
2024-03-27 21:24 ` dpdklab
2024-03-27 21:25 ` dpdklab
2024-03-27 21:27 ` dpdklab
2024-03-27 21:29 ` dpdklab
2024-03-27 21:29 ` dpdklab
2024-03-27 21:30 ` dpdklab
2024-03-27 21:30 ` dpdklab
2024-03-27 21:31 ` dpdklab
2024-03-27 21:31 ` dpdklab
2024-03-27 21:34 ` dpdklab
2024-03-27 21:38 ` dpdklab
2024-03-27 21:38 ` dpdklab
2024-03-27 21:39 ` dpdklab
2024-03-27 21:42 ` dpdklab
2024-03-27 21:42 ` dpdklab
2024-03-27 21:49 ` dpdklab
2024-03-27 21:49 ` dpdklab
2024-03-27 21:52 ` dpdklab
2024-03-27 21:58 ` dpdklab
2024-03-27 22:01 ` dpdklab
2024-03-27 22:02 ` dpdklab
2024-03-27 22:08 ` dpdklab
2024-03-27 22:19 ` dpdklab
2024-03-27 22:21 ` dpdklab
2024-03-27 22:30 ` dpdklab
2024-03-27 22:46 ` dpdklab
2024-03-27 22:58 ` dpdklab
2024-03-27 23:24 ` dpdklab
2024-03-27 23:26 ` dpdklab
2024-03-27 23:28 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-28  0:06 ` dpdklab
2024-04-02 11:20 ` dpdklab
2024-04-02 11:24 ` dpdklab
2024-04-02 11:28 ` dpdklab
2024-04-02 11:32 ` dpdklab
2024-04-02 11:51 ` 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=6604870c.050a0220.1f7ed.88ccSMTPIN_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).