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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw158854-158855 [PATCH] [2/2] net/mlx5: fix the masked val
Date: Mon, 17 Nov 2025 07:15:35 -0800 (PST)	[thread overview]
Message-ID: <691b3c17.050a0220.12e066.c049SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251117080942.9750-1-bingz@nvidia.com>

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

_Testing issues_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, November 17 2025 08:09:42 
DPDK git baseline: Repo:dpdk-next-net
  Branch: master
  CommitID:18d8a8909b8ed6b0a4bd8f99971da74ebba792e2

158854-158855 --> testing issues

Upstream job id: Template-DTS-Pipeline#255439

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
[2359/3635] Compiling C object drivers/librte_net_octeon_ep.so.26.0.p/meson-generated_.._rte_net_octeon_ep.pmd.c.o
[2360/3635] Compiling C object drivers/librte_net_octeon_ep.a.p/meson-generated_.._rte_net_octeon_ep.pmd.c.o
[2361/3635] Generating rte_net_pcap.pmd.c with a custom command
[2362/3635] Compiling C object drivers/librte_net_pfe_base_lib.a.p/net_qede_base_ecore_vf.c.o
[2363/3635] Linking target drivers/librte_net_ntnic.so.26.0
[2364/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_main.c.o
[2365/3635] Compiling C object drivers/librte_net_pfe_base_lib.a.p/net_qede_base_ecore_spq.c.o
[2366/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_sriov.c.o
[2367/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_regs.c.o
[2368/3635] Compiling C object drivers/librte_net_pfe_base_lib.a.p/net_qede_base_ecore_int.c.o
[2369/3635] Compiling C object drivers/librte_net_pfe_base_lib.a.p/net_qede_base_ecore_mcp.c.o
[2370/3635] Compiling C object drivers/librte_net_pfe_base_lib.a.p/net_qede_base_ecore_dev.c.o
[2371/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_filter.c.o
[2372/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_ethdev.c.o
[2373/3635] Compiling C object drivers/librte_net_pfe_base_lib.a.p/net_qede_base_ecore_sriov.c.o
[2374/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_rxtx.c.o
[2375/3635] Compiling C object drivers/libtmp_rte_net_qede.a.p/net_qede_qede_debug.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.2) 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/34624/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-11-17 15:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251117080942.9750-1-bingz@nvidia.com>
2025-11-17  7:48 ` |SUCCESS| pw158854-158855 [PATCH 2/2] net/mlx5: fix the masked value for a rule for sync API qemudev
2025-11-17  7:53 ` qemudev
2025-11-17  8:09 ` |WARNING| pw158855 " checkpatch
2025-11-17  9:19 ` |FAILURE| " 0-day Robot
2025-11-17  9:45 ` |SUCCESS| pw158854-158855 [PATCH] [2/2] net/mlx5: fix the masked val dpdklab
2025-11-17  9:45 ` |FAILURE| " dpdklab
2025-11-17  9:50 ` |SUCCESS| " dpdklab
2025-11-17  9:54 ` |FAILURE| " dpdklab
2025-11-17 10:12 ` |SUCCESS| " dpdklab
2025-11-17 11:50 ` |PENDING| " dpdklab
2025-11-17 12:48 ` |FAILURE| " dpdklab
2025-11-17 12:59 ` dpdklab
2025-11-17 13:00 ` dpdklab
2025-11-17 13:07 ` |SUCCESS| " dpdklab
2025-11-17 13:09 ` |FAILURE| " dpdklab
2025-11-17 13:09 ` dpdklab
2025-11-17 13:10 ` dpdklab
2025-11-17 13:13 ` dpdklab
2025-11-17 13:19 ` dpdklab
2025-11-17 13:20 ` dpdklab
2025-11-17 13:21 ` |PENDING| " dpdklab
2025-11-17 13:27 ` |FAILURE| " dpdklab
2025-11-17 13:33 ` dpdklab
2025-11-17 13:46 ` |PENDING| " dpdklab
2025-11-17 13:53 ` |FAILURE| " dpdklab
2025-11-17 14:14 ` dpdklab
2025-11-17 14:23 ` |WARNING| " dpdklab
2025-11-17 14:41 ` |FAILURE| " dpdklab
2025-11-17 14:45 ` dpdklab
2025-11-17 14:47 ` dpdklab
2025-11-17 14:59 ` dpdklab
2025-11-17 15:00 ` dpdklab
2025-11-17 15:01 ` dpdklab
2025-11-17 15:15 ` dpdklab
2025-11-17 15:15 ` dpdklab [this message]
2025-11-17 15:16 ` dpdklab
2025-11-17 15:18 ` dpdklab
2025-11-17 15:19 ` dpdklab
2025-11-17 15:19 ` dpdklab
2025-11-17 15:24 ` dpdklab
2025-11-17 15:27 ` dpdklab
2025-11-17 15:29 ` dpdklab
2025-11-17 15:53 ` dpdklab
2025-11-17 15:58 ` dpdklab
2025-11-17 16:25 ` |SUCCESS| " dpdklab
2025-11-17 16:48 ` dpdklab
2025-11-17 18:07 ` dpdklab
2025-11-17 18:21 ` dpdklab
2025-11-17 19:09 ` dpdklab
2025-11-17 19:26 ` 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=691b3c17.050a0220.12e066.c049SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).