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, Marek Pazdan <mpazdan@arista.com>
Subject: |WARNING| pw138855 [PATCH] igc/ixgbe: add get/set link settings inte
Date: Wed, 27 Mar 2024 05:55:36 -0700 (PDT)	[thread overview]
Message-ID: <66041748.170a0220.6c9e8.5f37SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240326235909.25276-1-mpazdan@arista.com>

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

_Testing issues_

Submitter: Marek Pazdan <mpazdan@arista.com>
Date: Tuesday, March 26 2024 23:59:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ded4d4765171b88470e59307f10625e942f22fca

138855 --> testing fail

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| Debian Bullseye | FAIL     |
+-----------------+----------+
| Fedora 39       | FAIL     |
+-----------------+----------+
| Fedora 38       | FAIL     |
+-----------------+----------+

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

1 function with some indirect sub-type change:

[C] 'function int rte_eth_link_get(uint16_t, rte_eth_link*)' at rte_ethdev.c:2972:1 has some indirect sub-type changes:
parameter 2 of type 'rte_eth_link*' has sub-type changes:
in pointed to type 'struct rte_eth_link' at rte_ethdev.h:336:1:
type size hasn't changed
2 data member changes:
'uint16_t link_autoneg' offset changed from 33 to 34 (in bits) (by +1 bits)
'uint16_t link_status' offset changed from 34 to 35 (in bits) (by +1 bits)

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_ethdev.so.24.0 build_install/usr/local/lib64/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 (1 filtered out) function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

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 ====

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

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

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

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

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 12:55 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240326235909.25276-1-mpazdan@arista.com>
2024-03-27  9:44 ` |SUCCESS| pw138855 [PATCH] igc/ixgbe: add get/set link settings interface qemudev
2024-03-27  9:49 ` qemudev
2024-03-27 10:08 ` |WARNING| " checkpatch
2024-03-27 12:49 ` |SUCCESS| pw138855 [PATCH] igc/ixgbe: add get/set link settings inte dpdklab
2024-03-27 12:52 ` dpdklab
2024-03-27 12:54 ` dpdklab
2024-03-27 12:54 ` dpdklab
2024-03-27 12:54 ` dpdklab
2024-03-27 12:55 ` dpdklab
2024-03-27 12:55 ` dpdklab [this message]
2024-03-27 12:55 ` dpdklab
2024-03-27 12:56 ` dpdklab
2024-03-27 12:57 ` dpdklab
2024-03-27 12:58 ` dpdklab
2024-03-27 12:58 ` |WARNING| " dpdklab
2024-03-27 12:59 ` dpdklab
2024-03-27 12:59 ` dpdklab
2024-03-27 12:59 ` |SUCCESS| " dpdklab
2024-03-27 13:02 ` |WARNING| " dpdklab
2024-03-27 13:03 ` dpdklab
2024-03-27 13:07 ` |SUCCESS| " dpdklab
2024-03-27 13:09 ` dpdklab
2024-03-27 13:11 ` dpdklab
2024-03-27 13:12 ` |WARNING| " dpdklab
2024-03-27 13:13 ` |SUCCESS| " dpdklab
2024-03-27 13:13 ` |WARNING| " dpdklab
2024-03-27 13:16 ` dpdklab
2024-03-27 13:19 ` |SUCCESS| " dpdklab
2024-03-27 13:21 ` dpdklab
2024-03-27 13:21 ` |WARNING| " dpdklab
2024-03-27 13:25 ` |SUCCESS| " dpdklab
2024-03-27 13:27 ` dpdklab
2024-03-27 13:27 ` |WARNING| " dpdklab
2024-03-27 13:30 ` |SUCCESS| " dpdklab
2024-03-27 13:32 ` dpdklab
2024-03-27 13:32 ` dpdklab
2024-03-27 13:35 ` dpdklab
2024-03-27 13:36 ` dpdklab
2024-03-27 13:41 ` dpdklab
2024-03-27 13:44 ` dpdklab
2024-03-27 13:45 ` dpdklab
2024-03-27 13:45 ` dpdklab
2024-03-27 13:47 ` dpdklab
2024-03-27 13:48 ` dpdklab
2024-03-27 13:49 ` dpdklab
2024-03-27 13:53 ` dpdklab
2024-03-27 13:53 ` dpdklab
2024-03-27 13:55 ` dpdklab
2024-03-27 13:55 ` dpdklab
2024-03-27 13:55 ` dpdklab
2024-03-27 13:56 ` dpdklab
2024-03-27 14:00 ` dpdklab
2024-03-27 14:00 ` dpdklab
2024-03-27 14:00 ` dpdklab
2024-03-27 14:00 ` dpdklab
2024-03-27 14:02 ` dpdklab
2024-03-27 14:03 ` dpdklab
2024-03-27 14:04 ` dpdklab
2024-03-27 14:04 ` dpdklab
2024-03-27 14:08 ` dpdklab
2024-03-27 14:10 ` dpdklab
2024-03-27 14:11 ` dpdklab
2024-03-27 14:11 ` dpdklab
2024-03-27 14:11 ` dpdklab
2024-03-27 14:12 ` dpdklab
2024-03-27 14:13 ` dpdklab
2024-03-27 14:13 ` dpdklab
2024-03-27 14:15 ` dpdklab
2024-03-27 14:17 ` dpdklab
2024-03-27 14:18 ` dpdklab
2024-03-27 14:19 ` dpdklab
2024-03-27 14:21 ` dpdklab
2024-03-27 14:22 ` dpdklab
2024-03-27 14:24 ` dpdklab
2024-03-27 14:27 ` dpdklab
2024-03-27 14:29 ` dpdklab
2024-03-27 14:32 ` dpdklab
2024-03-27 14:36 ` dpdklab
2024-03-27 14:40 ` dpdklab
2024-03-27 14:47 ` dpdklab
2024-03-27 14:52 ` dpdklab
2024-03-27 15:04 ` dpdklab
2024-03-27 15:04 ` dpdklab
2024-03-27 15:56 ` dpdklab
2024-03-27 16:36 ` dpdklab
2024-03-27 17:29 ` dpdklab
2024-04-02  9:27 ` dpdklab
2024-04-02  9:46 ` dpdklab
2024-04-02  9:50 ` dpdklab
2024-04-02  9:54 ` dpdklab
2024-04-02  9:58 ` 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=66041748.170a0220.6c9e8.5f37SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mpazdan@arista.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).