From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw137467 [PATCH] net/mlx5: fix sync meter processing in HW
Date: Thu, 29 Feb 2024 03:52:38 -0800 (PST) [thread overview]
Message-ID: <65e07006.b00a0220.1336c.37eeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229105614.593391-1-getelson@nvidia.com>
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/137467
_Testing issues_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, February 29 2024 10:56:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:45d2195f9ea6ead7242af856c799c6f084d874bc
137467 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | FAIL | PASS |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian 12 (arm) | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Windows Server 2019 (dpdk_meson_compile): ====
[593/827] Compiling C object drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.obj
[594/827] Generating symbol file drivers/rte_common_mlx5-24.dll.p/rte_common_mlx5-24.dll.symbols
[595/827] Generating rte_net_iavf_def with a custom command
[596/827] Compiling C object drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.obj
[597/827] Linking static target drivers/net/iavf/libiavf_avx512_lib.a
[598/827] Linking target drivers/rte_crypto_mlx5-24.dll
Creating library drivers\rte_crypto_mlx5.lib and object drivers\rte_crypto_mlx5.exp
[599/827] Linking target drivers/rte_net_mlx5-24.dll
FAILED: drivers/rte_net_mlx5-24.dll
"clang" @drivers/rte_net_mlx5-24.dll.rsp
Creating library drivers\rte_net_mlx5.lib and object drivers\rte_net_mlx5.exp
net_mlx5_mlx5_flow_meter.c.obj : error LNK2019: unresolved external symbol mlx5_flow_action_job_init referenced in function mlx5_flow_meter_hws_create
drivers\rte_net_mlx5-24.dll : fatal error LNK1120: 1 unresolved externals
clang: error: linker command failed with exit code 1120 (use -v to see invocation)
[600/827] Linking static target drivers/net/i40e/libi40e_avx512_lib.a
[601/827] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_tm.c.obj
[602/827] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_rxtx_vec_sse.c.obj
[603/827] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_fdir.c.obj
[604/827] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_controlq.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.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)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29330/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-29 11:52 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229105614.593391-1-getelson@nvidia.com>
2024-02-29 10:34 ` |SUCCESS| pw137467 [PATCH] net/mlx5: fix sync meter processing in HWS setup qemudev
2024-02-29 10:38 ` qemudev
2024-02-29 10:57 ` |WARNING| " checkpatch
2024-02-29 11:33 ` |FAILURE| pw137467 [PATCH] net/mlx5: fix sync meter processing in HW dpdklab
2024-02-29 11:34 ` dpdklab
2024-02-29 11:35 ` |SUCCESS| " dpdklab
2024-02-29 11:36 ` |FAILURE| " dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` |SUCCESS| " dpdklab
2024-02-29 11:37 ` dpdklab
2024-02-29 11:37 ` |FAILURE| " dpdklab
2024-02-29 11:37 ` |SUCCESS| " dpdklab
2024-02-29 11:37 ` |FAILURE| " dpdklab
2024-02-29 11:37 ` |SUCCESS| " dpdklab
2024-02-29 11:38 ` dpdklab
2024-02-29 11:39 ` dpdklab
2024-02-29 11:45 ` |FAILURE| " dpdklab
2024-02-29 11:46 ` |SUCCESS| " dpdklab
2024-02-29 11:46 ` |FAILURE| " dpdklab
2024-02-29 11:46 ` |SUCCESS| " dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 11:47 ` |FAILURE| " dpdklab
2024-02-29 11:47 ` |SUCCESS| " dpdklab
2024-02-29 11:47 ` |FAILURE| " dpdklab
2024-02-29 11:48 ` |SUCCESS| " dpdklab
2024-02-29 11:48 ` dpdklab
2024-02-29 11:48 ` |FAILURE| " dpdklab
2024-02-29 11:48 ` |SUCCESS| " dpdklab
2024-02-29 11:48 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:52 ` dpdklab
2024-02-29 11:52 ` dpdklab [this message]
2024-02-29 11:53 ` dpdklab
2024-02-29 11:53 ` dpdklab
2024-02-29 11:53 ` dpdklab
2024-02-29 11:56 ` dpdklab
2024-02-29 11:57 ` dpdklab
2024-02-29 11:57 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 12:03 ` dpdklab
2024-02-29 12:04 ` |FAILURE| " dpdklab
2024-02-29 12:04 ` |SUCCESS| " dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:06 ` dpdklab
2024-02-29 12:06 ` dpdklab
2024-02-29 12:10 ` dpdklab
2024-02-29 12:10 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:12 ` dpdklab
2024-02-29 12:59 ` dpdklab
2024-02-29 13:35 ` dpdklab
2024-03-01 4:53 ` dpdklab
2024-03-01 5:00 ` dpdklab
2024-03-01 5:16 ` dpdklab
2024-03-01 5:21 ` dpdklab
2024-03-02 4:05 ` dpdklab
2024-03-02 17:17 ` dpdklab
2024-03-02 17:50 ` dpdklab
2024-03-02 18:22 ` 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=65e07006.b00a0220.1336c.37eeSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=getelson@nvidia.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).