From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, "Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw97206 [PATCH] net/virtio: wait device ready in device reset
Date: Mon, 23 Aug 2021 20:32:25 -0400 (EDT) [thread overview]
Message-ID: <20210824003225.B9F3388E70@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 5624 bytes --]
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/97206
_Testing issues_
Submitter: Xueming(Steven) Li <xuemingl@nvidia.com>
Date: Monday, August 23 2021 06:39:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fdab8f2e17493192d555cd88cf28b06269174326
97206 --> testing fail
Test environment and result as below:
+------------------------------------+----------+
| Environment | abi_test |
+====================================+==========+
| Ubuntu 20.04 ARM | FAIL |
+------------------------------------+----------+
| FreeBSD 13 | FAIL |
+------------------------------------+----------+
| Ubuntu 18.04 | FAIL |
+------------------------------------+----------+
| RHEL 7 | FAIL |
+------------------------------------+----------+
| RHEL8 | FAIL |
+------------------------------------+----------+
| Ubuntu 20.04 | FAIL |
+------------------------------------+----------+
| Arch Linux | FAIL |
+------------------------------------+----------+
| CentOS 8 | FAIL |
+------------------------------------+----------+
| Fedora 31 | FAIL |
+------------------------------------+----------+
| openSUSE Leap 15 | FAIL |
+------------------------------------+----------+
| CentOS Stream 8 | FAIL |
+------------------------------------+----------+
| Fedora 32 | FAIL |
+------------------------------------+----------+
| Fedora 34 | FAIL |
+------------------------------------+----------+
| Fedora 34 clang | FAIL |
+------------------------------------+----------+
| Fedora 33 | FAIL |
+------------------------------------+----------+
| Ubuntu 20.04 ARM cross-compilation | FAIL |
+------------------------------------+----------+
==== 20 line log output for Ubuntu 20.04 ARM cross-compilation (abi_test): ====
[D] 'function int rte_vhost_get_mtu(int, uint16_t*)' {rte_vhost_get_mtu@@DPDK_21}
[D] 'function int rte_vhost_get_negotiated_features(int, uint64_t*)' {rte_vhost_get_negotiated_features@@DPDK_21}
[D] 'function int rte_vhost_get_numa_node(int)' {rte_vhost_get_numa_node@@DPDK_21}
[D] 'function uint32_t rte_vhost_get_queue_num(int)' {rte_vhost_get_queue_num@@DPDK_21}
[D] 'function rte_vdpa_device* rte_vhost_get_vdpa_device(int)' {rte_vhost_get_vdpa_device@@DPDK_21}
[D] 'function int rte_vhost_get_vhost_vring(int, uint16_t, rte_vhost_vring*)' {rte_vhost_get_vhost_vring@@DPDK_21}
[D] 'function int rte_vhost_get_vring_base(int, uint16_t, uint16_t*, uint16_t*)' {rte_vhost_get_vring_base@@DPDK_21}
[D] 'function uint16_t rte_vhost_get_vring_num(int)' {rte_vhost_get_vring_num@@DPDK_21}
[D] 'function int rte_vhost_host_notifier_ctrl(int, uint16_t, bool)' {rte_vhost_host_notifier_ctrl@@DPDK_21}
[D] 'function void rte_vhost_log_used_vring(int, uint16_t, uint64_t, uint64_t)' {rte_vhost_log_used_vring@@DPDK_21}
[D] 'function void rte_vhost_log_write(int, uint64_t, uint64_t)' {rte_vhost_log_write@@DPDK_21}
[D] 'function uint32_t rte_vhost_rx_queue_count(int, uint16_t)' {rte_vhost_rx_queue_count@@DPDK_21}
[D] 'function int rte_vhost_set_vring_base(int, uint16_t, uint16_t, uint16_t)' {rte_vhost_set_vring_base@@DPDK_21}
[D] 'function int rte_vhost_vring_call(int, uint16_t)' {rte_vhost_vring_call@@DPDK_21}
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_vhost.dump build_install/dump/librte_vhost.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
ABIDIFF_ABI_INCOMPATIBLE_CHANGE, this change breaks the ABI.
==== End log output ====
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
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)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Ubuntu 20.04 ARM cross-compilation
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18301/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-08-24 0:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210824003225.B9F3388E70@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--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).