From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw154799-154801 [PATCH] [v3,5/5] net/mlx5: use consecutive
Date: Sat, 28 Jun 2025 12:00:54 -0700 (PDT) [thread overview]
Message-ID: <68603be6.920a0220.2d396b.efebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250627163729.50460-6-bingz@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/154801
_Testing issues_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Friday, June 27 2025 16:37:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5c0c1a13c34aa57c6e18f9ba852a9b5807c58b72
154799-154801 --> testing issues
Upstream job id: ACVP-FIPS-testing#10323
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+==============+======================+======================+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | WARN |
+--------------+----------------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
| ^~
cc1: all warnings being treated as errors
[1977/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rss.c.o
[1978/3553] Linking target drivers/librte_net_ionic.so.25.2
[1979/3553] Linking target drivers/librte_net_idpf.so.25.2
[1980/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_geneve.c.o
[1981/3553] Compiling C object drivers/libtmp_rte_net_mlx4.a.p/net_mlx4_mlx4_rxtx.c.o
[1982/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxmode.c.o
[1983/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_flex.c.o
[1984/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_aso.c.o
[1985/3553] Compiling C object drivers/libtmp_rte_net_memif.a.p/net_memif_rte_eth_memif.c.o
[1986/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxtx.c.o
[1987/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_stats.c.o
[1988/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o
[1989/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxq.c.o
[1990/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_meter.c.o
[1991/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.o
[1992/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rx.c.o
[1993/3553] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_dv.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33530/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-06-28 19:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250627163729.50460-6-bingz@nvidia.com>
2025-06-27 16:05 ` |SUCCESS| pw154799-154801 [PATCH v3 5/5] net/mlx5: use consecutive memory for Tx queue creation qemudev
2025-06-27 16:10 ` qemudev
2025-06-27 16:37 ` |SUCCESS| pw154801 " checkpatch
2025-06-27 18:07 ` |FAILURE| " 0-day Robot
2025-06-27 19:04 ` |SUCCESS| pw154799-154801 [PATCH] [v3,5/5] net/mlx5: use consecutive dpdklab
2025-06-27 19:08 ` dpdklab
2025-06-27 19:23 ` |FAILURE| " dpdklab
2025-06-27 19:27 ` dpdklab
2025-06-27 20:00 ` dpdklab
2025-06-27 20:04 ` |PENDING| " dpdklab
2025-06-27 20:49 ` |SUCCESS| " dpdklab
2025-06-27 20:50 ` |FAILURE| " dpdklab
2025-06-27 21:01 ` |SUCCESS| " dpdklab
2025-06-27 21:36 ` dpdklab
2025-06-27 22:00 ` |FAILURE| " dpdklab
2025-06-27 22:42 ` dpdklab
2025-06-27 23:00 ` dpdklab
2025-06-27 23:01 ` dpdklab
2025-06-27 23:04 ` dpdklab
2025-06-27 23:06 ` dpdklab
2025-06-27 23:08 ` dpdklab
2025-06-27 23:12 ` |WARNING| " dpdklab
2025-06-27 23:16 ` |PENDING| " dpdklab
2025-06-27 23:32 ` |FAILURE| " dpdklab
2025-06-27 23:53 ` |SUCCESS| " dpdklab
2025-06-27 23:54 ` dpdklab
2025-06-27 23:55 ` dpdklab
2025-06-27 23:56 ` |PENDING| " dpdklab
2025-06-28 0:03 ` |FAILURE| " dpdklab
2025-06-28 0:32 ` dpdklab
2025-06-28 1:25 ` |WARNING| " dpdklab
2025-06-28 2:52 ` |FAILURE| " dpdklab
2025-06-28 19:00 ` dpdklab [this message]
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=68603be6.920a0220.2d396b.efebSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).