automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw141123 [PATCH] net/mlx5: add non-template flow metadata
Date: Thu, 13 Jun 2024 09:52:34 -0700 (PDT)	[thread overview]
Message-ID: <666b23d2.050a0220.5ca83.2ab9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240613125146.547992-1-bingz@nvidia.com>

Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/141123

_Testing issues_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thursday, June 13 2024 12:51:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e

141123 --> 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): ====
|                         ^~~~~~~
../drivers/net/mlx5/linux/mlx5_os.c:511:25: note: each undeclared identifier is reported only once for each function it appears in
../drivers/net/mlx5/linux/mlx5_os.c:517:11: error: 'struct mlx5_dev_ctx_shared' has no member named 'mreg_cp_tbl'
517 |    if (!sh->mreg_cp_tbl) {
|           ^~
[1754/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_socket.c.o'.
[1755/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_hws_cnt.c.o'.
[1756/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_linux_mlx5_flow_os.c.o'.
[1757/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_verbs.c.o'.
[1758/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_mpw.c.o'.
[1759/2897] Generating rte_net_ixgbe.sym_chk with a meson_exe.py custom command.
[1760/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_hws_mlx5dr_context.c.o'.
[1761/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxtx_vec.c.o'.
[1762/2897] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
[1763/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_dv.c.o'.
[1764/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_nompw.c.o'.
[1765/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_empw.c.o'.
[1766/2897] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_hw.c.o'.
[1767/2897] 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/30180/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-06-13 16:52 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240613125146.547992-1-bingz@nvidia.com>
2024-06-13 12:29 ` |SUCCESS| pw141123 [PATCH] net/mlx5: add non-template flow metadata split qemudev
2024-06-13 12:34 ` qemudev
2024-06-13 12:53 ` |WARNING| " checkpatch
2024-06-13 16:04 ` |WARNING| pw141123 [PATCH] net/mlx5: add non-template flow metadata dpdklab
2024-06-13 16:04 ` dpdklab
2024-06-13 16:05 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:44 ` dpdklab
2024-06-13 16:46 ` |FAILURE| " dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab [this message]
2024-06-13 16:52 ` dpdklab
2024-06-13 16:54 ` dpdklab
2024-06-13 16:55 ` dpdklab
2024-06-13 16:55 ` dpdklab
2024-06-13 16:56 ` dpdklab
2024-06-13 16:57 ` dpdklab
2024-06-13 16:57 ` dpdklab
2024-06-13 16:59 ` dpdklab
2024-06-13 16:59 ` dpdklab
2024-06-13 16:59 ` dpdklab
2024-06-13 17:00 ` dpdklab
2024-06-13 17:00 ` dpdklab
2024-06-13 17:04 ` dpdklab
2024-06-13 17:06 ` dpdklab
2024-06-13 17:07 ` dpdklab
2024-06-13 17:08 ` dpdklab
2024-06-13 17:09 ` dpdklab
2024-06-13 17:09 ` dpdklab
2024-06-13 17:10 ` dpdklab
2024-06-13 17:10 ` dpdklab
2024-06-13 17:18 ` dpdklab
2024-06-13 17:22 ` dpdklab
2024-06-13 17:22 ` dpdklab
2024-06-13 17:22 ` dpdklab
2024-06-13 17:23 ` dpdklab
2024-06-13 17:23 ` dpdklab
2024-06-13 17:24 ` dpdklab
2024-06-13 17:25 ` dpdklab
2024-06-13 17:25 ` dpdklab
2024-06-13 17:26 ` dpdklab
2024-06-13 17:26 ` dpdklab
2024-06-13 17:27 ` dpdklab
2024-06-13 17:28 ` dpdklab
2024-06-13 17:28 ` dpdklab
2024-06-13 17:29 ` dpdklab
2024-06-13 17:29 ` dpdklab
2024-06-13 17:30 ` dpdklab
2024-06-13 17:31 ` dpdklab
2024-06-13 17:32 ` dpdklab
2024-06-13 17:34 ` dpdklab
2024-06-13 17:35 ` dpdklab
2024-06-13 17:38 ` dpdklab
2024-06-13 17:39 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:44 ` 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=666b23d2.050a0220.5ca83.2ab9SMTPIN_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).