From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Jie Hai <haijie1@huawei.com>,
dpdk-test-reports@iol.unh.edu, Jie Hai <haijie1@huawei.com>
Subject: |WARNING| pw136898-136903 [PATCH] [v3,7/7] net/hns3: support filter
Date: Tue, 20 Feb 2024 05:19:25 -0800 (PST) [thread overview]
Message-ID: <65d4a6dd.810a0220.34228.8d37SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/136903
_Testing issues_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Tuesday, February 20 2024 10:58:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa24b3f588b31ee9699f6b2dde8d12c0453448d1
136898-136903 --> testing fail
Test environment and result as below:
+---------------+----------+
| Environment | abi_test |
+===============+==========+
| Debian Buster | FAIL |
+---------------+----------+
==== 20 line log output for Debian Buster (abi_test): ====
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed, 1 Changed (39 filtered out), 0 Added (7 filtered out) functions
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_dev_get_reg_info(uint16_t, rte_dev_reg_info*)' at rte_ethdev.c:6390:1 has some indirect sub-type changes:
parameter 2 of type 'rte_dev_reg_info*' has sub-type changes:
in pointed to type 'struct rte_dev_reg_info' at rte_dev_info.h:22:1:
type size changed from 192 to 320 (in bits)
2 data member insertions:
'char* filter', at offset 192 (in bits) at rte_dev_info.h:32:1
'rte_eth_reg_name* names', at offset 256 (in bits) at rte_dev_info.h:33:1
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).
==== End log output ====
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29190/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-20 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 13:19 dpdklab [this message]
2024-02-20 13:21 dpdklab
2024-02-20 13:23 dpdklab
2024-02-20 13:24 dpdklab
2024-02-20 13:27 dpdklab
2024-02-20 13:27 dpdklab
2024-02-20 13:29 dpdklab
2024-02-20 13:29 dpdklab
2024-02-20 13:30 dpdklab
2024-02-20 13:35 dpdklab
2024-02-20 13:35 dpdklab
2024-02-20 13:41 dpdklab
2024-02-20 13:47 dpdklab
2024-02-20 13:48 dpdklab
2024-02-20 13:49 dpdklab
2024-02-20 13:54 dpdklab
2024-02-20 13:57 dpdklab
2024-02-20 14:03 dpdklab
2024-02-20 14:07 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=65d4a6dd.810a0220.34228.8d37SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=haijie1@huawei.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).