From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw141110-141117 [PATCH] [v2,8/8] net/mlx5: add async flow
Date: Wed, 12 Jun 2024 21:55:09 -0700 (PDT) [thread overview]
Message-ID: <666a7bad.630a0220.f4de0.158fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240612162426.978117-9-dsosnowski@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/141117
_Testing issues_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, June 12 2024 16:24:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e
141110-141117 --> testing issues
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN |
+--------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
| RTE_FLOW_CONV_OP_ITEM_NAME
../drivers/net/mlx5/mlx5_flow_hw.c:16208:24: note: each undeclared identifier is reported only once for each function it appears in
[1764/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxtx_vec.c.o'.
[1765/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_mp_os.c.o'.
[1766/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_flow_os.c.o'.
[1767/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_verbs.c.o'.
[1768/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_buddy.c.o'.
[1769/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_rule.c.o'.
[1770/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_matcher.c.o'.
[1771/2896] Generating rte_net_ixgbe.sym_chk with a meson_exe.py custom command.
[1772/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_pool.c.o'.
[1773/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_cmd.c.o'.
[1774/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_action.c.o'.
[1775/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_dv.c.o'.
[1776/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_definer.c.o'.
[1777/2896] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
[1778/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_empw.c.o'.
[1779/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_nompw.c.o'.
[1780/2896] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_txpp.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30175/
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-06-13 4:57 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240612162426.978117-9-dsosnowski@nvidia.com>
2024-06-12 16:00 ` |SUCCESS| pw141110-141117 [PATCH v2 8/8] net/mlx5: add async flow operation validation qemudev
2024-06-12 16:05 ` qemudev
2024-06-12 16:26 ` |SUCCESS| pw141117 " checkpatch
2024-06-13 2:00 ` |WARNING| pw141110-141117 [PATCH] [v2,8/8] net/mlx5: add async flow dpdklab
2024-06-13 2:12 ` dpdklab
2024-06-13 2:41 ` dpdklab
2024-06-13 2:42 ` dpdklab
2024-06-13 3:26 ` dpdklab
2024-06-13 3:32 ` dpdklab
2024-06-13 3:38 ` dpdklab
2024-06-13 3:43 ` dpdklab
2024-06-13 3:56 ` dpdklab
2024-06-13 4:17 ` dpdklab
2024-06-13 4:18 ` dpdklab
2024-06-13 4:50 ` |FAILURE| " dpdklab
2024-06-13 4:50 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:51 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:52 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:53 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:54 ` dpdklab
2024-06-13 4:55 ` dpdklab [this message]
2024-06-13 4:55 ` dpdklab
2024-06-13 4:55 ` dpdklab
2024-06-13 4:56 ` dpdklab
2024-06-13 4:56 ` dpdklab
2024-06-13 4:56 ` dpdklab
2024-06-13 4:57 ` dpdklab
2024-06-13 4:57 ` dpdklab
2024-06-13 4:57 ` |WARNING| " dpdklab
2024-06-13 4:58 ` |FAILURE| " dpdklab
2024-06-13 4:58 ` dpdklab
2024-06-13 4:58 ` dpdklab
2024-06-13 4:59 ` dpdklab
2024-06-13 4:59 ` dpdklab
2024-06-13 5:00 ` dpdklab
2024-06-13 5:00 ` dpdklab
2024-06-13 5:00 ` dpdklab
2024-06-13 5:01 ` dpdklab
2024-06-13 5:01 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:02 ` dpdklab
2024-06-13 5:03 ` dpdklab
2024-06-13 5:03 ` dpdklab
2024-06-13 5:04 ` dpdklab
2024-06-13 5:04 ` dpdklab
2024-06-13 5:04 ` dpdklab
2024-06-13 5:05 ` dpdklab
2024-06-13 5:06 ` dpdklab
2024-06-13 5:07 ` dpdklab
2024-06-13 5:07 ` dpdklab
2024-06-13 5:10 ` dpdklab
2024-06-13 5:10 ` |WARNING| " dpdklab
2024-06-13 5:10 ` |FAILURE| " dpdklab
2024-06-13 5:22 ` dpdklab
2024-06-13 5:22 ` dpdklab
2024-06-13 5:23 ` dpdklab
2024-06-13 5:23 ` dpdklab
2024-06-13 5:24 ` dpdklab
2024-06-13 5:25 ` dpdklab
2024-06-13 5:31 ` 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=666a7bad.630a0220.f4de0.158fSMTPIN_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).