From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Tomer Shmilovich <tshmilovich@nvidia.com>
Subject: |FAILURE| pw131971 [PATCH] net/mlx5: supporting group set miss actio
Date: Tue, 26 Sep 2023 16:53:15 -0700 (PDT) [thread overview]
Message-ID: <65136eeb.050a0220.4f8b9.016fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/131971
_Testing issues_
Submitter: Tomer Shmilovich <tshmilovich@nvidia.com>
Date: Tuesday, September 26 2023 15:58:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d58c97481a136ad5342c9d8717b22bdaa5eccd43
131971 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Debian Buster | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
| Fedora 38 | FAIL |
+---------------------+----------------+
| RHEL8 | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
| Ubuntu 22.04 | FAIL |
+---------------------+----------------+
==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
../drivers/net/mlx5/mlx5_flow.c:1031:1: note: previous declaration of 'mlx5_flow_group_set_miss_actions' with type 'int(struct rte_eth_dev *, uint32_t, const struct rte_flow_group_attr *, const struct rte_flow_action *, struct rte_flow_error *)' {aka 'int(struct rte_eth_dev *, unsigned int, const struct rte_flow_group_attr *, const struct rte_flow_action *, struct rte_flow_error *)'}
1031 | mlx5_flow_group_set_miss_actions(struct rte_eth_dev *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow.c: In function 'mlx5_flow_group_set_miss_actions':
../drivers/net/mlx5/mlx5_flow.c:9327:60: error: passing argument 3 of 'fops->group_set_miss_actions' from incompatible pointer type [-Werror=incompatible-pointer-types]
9327 | return fops->group_set_miss_actions(dev, group_id, attr, actions, error);
| ^~~~
| |
| const struct rte_flow_group_attr *
../drivers/net/mlx5/mlx5_flow.c:9327:60: note: expected 'const struct rte_flow_group_attr *' but argument is of type 'const struct rte_flow_group_attr *'
../drivers/net/mlx5/mlx5_flow.c: At top level:
../drivers/net/mlx5/mlx5_flow.c:1031:1: error: 'mlx5_flow_group_set_miss_actions' used but never defined [-Werror]
1031 | mlx5_flow_group_set_miss_actions(struct rte_eth_dev *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow.c:9312:1: error: 'mlx5_flow_group_set_miss_actions' defined but not used [-Werror=unused-function]
9312 | mlx5_flow_group_set_miss_actions(struct rte_eth_dev *dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[1632/2705] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
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: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27736/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-26 23:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 23:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-26 23:54 dpdklab
2023-09-26 23:54 dpdklab
2023-09-26 23:53 dpdklab
2023-09-26 23:52 dpdklab
2023-09-26 23:51 dpdklab
2023-09-26 23:45 dpdklab
2023-09-26 23:38 dpdklab
2023-09-26 23:31 dpdklab
2023-09-26 23:30 dpdklab
2023-09-26 23:29 dpdklab
2023-09-26 22:25 dpdklab
2023-09-26 22:25 dpdklab
2023-09-26 22:24 dpdklab
2023-09-26 22:01 dpdklab
2023-09-26 22:01 dpdklab
2023-09-26 21:58 dpdklab
2023-09-26 21:57 dpdklab
2023-09-26 21:57 dpdklab
2023-09-26 21:57 dpdklab
2023-09-26 21:56 dpdklab
2023-09-26 21:56 dpdklab
2023-09-26 21:55 dpdklab
2023-09-26 21:53 dpdklab
2023-09-26 21:53 dpdklab
2023-09-26 21:52 dpdklab
2023-09-26 21:52 dpdklab
2023-09-26 21:52 dpdklab
2023-09-26 21:51 dpdklab
2023-09-26 21:48 dpdklab
2023-09-26 21:48 dpdklab
2023-09-26 21:46 dpdklab
2023-09-26 21:39 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=65136eeb.050a0220.4f8b9.016fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=tshmilovich@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).