From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Dong Zhou <dongzhou@nvidia.com>
Subject: |WARNING| pw128202-128201 [PATCH] [v1,2/2] net/mlx5/hws: add support
Date: Thu, 08 Jun 2023 14:36:16 -0700 (PDT) [thread overview]
Message-ID: <648249d0.020a0220.d72af.2a2eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/128201
_Testing issues_
Submitter: Dong Zhou <dongzhou@nvidia.com>
Date: Tuesday, June 06 2023 11:07:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38689022f609a290645c7027084aee720c1fcf91
128202-128201 --> testing fail
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| openSUSE Leap 15 | FAIL |
+------------------+----------+
| Debian Bullseye | FAIL |
+------------------+----------+
| Ubuntu 22.04 | FAIL |
+------------------+----------+
| RHEL 7 | FAIL |
+------------------+----------+
| CentOS Stream 9 | FAIL |
+------------------+----------+
| Debian Buster | FAIL |
+------------------+----------+
| RHEL8 | FAIL |
+------------------+----------+
| CentOS Stream 8 | FAIL |
+------------------+----------+
| Fedora 38 | FAIL |
+------------------+----------+
| Fedora 37 | FAIL |
+------------------+----------+
==== 20 line log output for Fedora 37 (abi_test): ====
11065 | bth_v->hdr.opcode & bth_m->hdr.opcode);
| ^~
../drivers/common/mlx5/mlx5_prm.h:867:26: note: in definition of macro 'MLX5_SET'
867 | u32 _v = v; \
| ^
../drivers/net/mlx5/mlx5_flow_dv.c:11067:28: error: invalid use of undefined type 'const struct rte_flow_item_ib_bth'
11067 | size = sizeof(bth_m->hdr.dst_qp);
| ^~
../drivers/net/mlx5/mlx5_flow_dv.c:11069:33: error: invalid use of undefined type 'const struct rte_flow_item_ib_bth'
11069 | qpn_v[i] = bth_m->hdr.dst_qp[i] & bth_v->hdr.dst_qp[i];
| ^~
../drivers/net/mlx5/mlx5_flow_dv.c:11069:56: error: invalid use of undefined type 'const struct rte_flow_item_ib_bth'
11069 | qpn_v[i] = bth_m->hdr.dst_qp[i] & bth_v->hdr.dst_qp[i];
| ^~
../drivers/net/mlx5/mlx5_flow_dv.c: In function 'flow_dv_translate_items':
../drivers/net/mlx5/mlx5_flow_dv.c:13873:14: error: 'RTE_FLOW_ITEM_TYPE_IB_BTH' undeclared (first use in this function); did you mean 'RTE_FLOW_ITEM_TYPE_ETH'?
13873 | case RTE_FLOW_ITEM_TYPE_IB_BTH:
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| RTE_FLOW_ITEM_TYPE_ETH
ninja: build stopped: subcommand failed.
==== End log output ====
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
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)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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/26551/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-08 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 21:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:36 dpdklab
2023-06-08 21:35 dpdklab
2023-06-08 21:35 dpdklab
2023-06-08 21:30 dpdklab
2023-06-06 14: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=648249d0.020a0220.d72af.2a2eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dongzhou@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).