From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw152125 [PATCH] net/mlx5: fix LACP packets handling in is
Date: Sat, 01 Mar 2025 18:02:03 -0800 (PST) [thread overview]
Message-ID: <67c3bc1b.170a0220.3802e0.14ccSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250227102045.89381-1-mkashani@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/152125
_Testing issues_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Thursday, February 27 2025 10:20:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5813fc4238f10b5cc2aa008b0116c977712820d7
152125 --> testing issues
Upstream job id: ACVP-FIPS-testing#9098
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| 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
[2088/3181] Linking static target drivers/libtmp_rte_net_r8169.a
[2089/3181] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_debug.c.o
[2090/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_sriov.c.o
[2091/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mcdi.c.o
[2092/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_kvargs.c.o
[2093/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc.c.o
[2094/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_intr.c.o
[2095/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_tso.c.o
[2096/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_ev.c.o
[2097/3181] Compiling C object drivers/libtmp_rte_net_ring.a.p/net_ring_rte_eth_ring.c.o
[2098/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_filter.c.o
[2099/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_port.c.o
[2100/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_ethdev.c.o
[2101/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_sw_stats.c.o
[2102/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_tx.c.o
[2103/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_rx.c.o
[2104/3181] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32704/
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:[~2025-03-02 2:02 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250227102045.89381-1-mkashani@nvidia.com>
2025-02-27 9:47 ` |SUCCESS| pw152125 [PATCH] net/mlx5: fix LACP packets handling in isolated mode qemudev
2025-02-27 9:51 ` qemudev
2025-02-27 10:22 ` checkpatch
2025-02-27 11:26 ` 0-day Robot
2025-02-28 6:01 ` |SUCCESS| pw152125 [PATCH] net/mlx5: fix LACP packets handling in is dpdklab
2025-02-28 6:14 ` |PENDING| " dpdklab
2025-02-28 6:15 ` |SUCCESS| " dpdklab
2025-02-28 6:25 ` dpdklab
2025-02-28 6:37 ` dpdklab
2025-02-28 6:42 ` dpdklab
2025-02-28 6:42 ` dpdklab
2025-02-28 6:44 ` dpdklab
2025-02-28 6:58 ` dpdklab
2025-02-28 7:03 ` dpdklab
2025-02-28 7:13 ` dpdklab
2025-02-28 7:14 ` dpdklab
2025-02-28 7:19 ` dpdklab
2025-02-28 7:25 ` |PENDING| " dpdklab
2025-02-28 7:40 ` dpdklab
2025-02-28 7:52 ` |FAILURE| " dpdklab
2025-02-28 8:05 ` |SUCCESS| " dpdklab
2025-02-28 8:08 ` |PENDING| " dpdklab
2025-02-28 8:11 ` |SUCCESS| " dpdklab
2025-02-28 8:32 ` |PENDING| " dpdklab
2025-02-28 8:47 ` |FAILURE| " dpdklab
2025-02-28 8:48 ` dpdklab
2025-02-28 8:57 ` |SUCCESS| " dpdklab
2025-02-28 8:59 ` |WARNING| " dpdklab
2025-02-28 9:02 ` |FAILURE| " dpdklab
2025-02-28 9:02 ` |SUCCESS| " dpdklab
2025-02-28 9:23 ` |WARNING| " dpdklab
2025-02-28 9:24 ` dpdklab
2025-02-28 9:40 ` |SUCCESS| " dpdklab
2025-02-28 9:48 ` dpdklab
2025-02-28 10:03 ` dpdklab
2025-02-28 10:19 ` |FAILURE| " dpdklab
2025-02-28 10:22 ` dpdklab
2025-02-28 11:06 ` |PENDING| " dpdklab
2025-02-28 11:26 ` |FAILURE| " dpdklab
2025-02-28 11:32 ` |PENDING| " dpdklab
2025-02-28 11:35 ` |FAILURE| " dpdklab
2025-02-28 11:37 ` |WARNING| " dpdklab
2025-02-28 12:04 ` dpdklab
2025-02-28 13:01 ` |FAILURE| " dpdklab
2025-02-28 13:23 ` dpdklab
2025-02-28 22:24 ` dpdklab
2025-03-01 0:29 ` dpdklab
2025-03-01 4:12 ` |WARNING| " dpdklab
2025-03-01 7:31 ` dpdklab
2025-03-02 2:02 ` dpdklab [this message]
2025-03-02 2:51 ` |FAILURE| " dpdklab
2025-03-02 2:54 ` dpdklab
2025-03-02 3:00 ` |WARNING| " dpdklab
2025-03-02 3:19 ` |FAILURE| " dpdklab
2025-03-02 3:20 ` 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=67c3bc1b.170a0220.3802e0.14ccSMTPIN_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).