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| pw152130 [PATCH] net/mlx5: fix GTP flags matching
Date: Sat, 01 Mar 2025 11:38:15 -0800 (PST)	[thread overview]
Message-ID: <67c36227.050a0220.1c58ab.166aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250227104941.93927-1-mkashani@nvidia.com>

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

_Testing issues_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Thursday, February 27 2025 10:49:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5813fc4238f10b5cc2aa008b0116c977712820d7

152130 --> testing issues

Upstream job id: ACVP-FIPS-testing#9087

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
[2136/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mae.c.o
[2137/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_repr.c.o
[2138/3181] Generating rte_net_ring.sym_chk with a custom command (wrapped by meson to capture output)
[2139/3181] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_mempool.c.o
[2140/3181] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_swq.c.o
[2141/3181] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_pipeline.c.o
[2142/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_repr_proxy.c.o
[2143/3181] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic.c.o
[2144/3181] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_netlink.c.o
[2145/3181] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_ef10_tx.c.o
[2146/3181] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_intr.c.o
[2147/3181] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_thread.c.o
[2148/3181] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.o
[2149/3181] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_cli.c.o
[2150/3181] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_flow.c.o
[2151/3181] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[2152/3181] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_rte_eth_tap.c.o
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/32708/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-03-01 19:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250227104941.93927-1-mkashani@nvidia.com>
2025-02-27 10:21 ` |SUCCESS| " qemudev
2025-02-27 10:25 ` qemudev
2025-02-27 10:51 ` checkpatch
2025-02-27 12:44 ` 0-day Robot
2025-02-27 17:37 ` dpdklab
2025-02-27 17:40 ` dpdklab
2025-02-27 17:44 ` dpdklab
2025-02-27 17:50 ` dpdklab
2025-02-27 17:52 ` dpdklab
2025-02-27 17:58 ` dpdklab
2025-02-27 18:03 ` dpdklab
2025-02-27 18:15 ` dpdklab
2025-02-27 18:31 ` |PENDING| " dpdklab
2025-02-27 19:45 ` |SUCCESS| " dpdklab
2025-02-27 20:18 ` |FAILURE| " dpdklab
2025-02-27 20:20 ` |PENDING| " dpdklab
2025-02-27 20:29 ` dpdklab
2025-02-27 20:32 ` |FAILURE| " dpdklab
2025-02-27 20:34 ` dpdklab
2025-02-27 20:34 ` dpdklab
2025-02-27 20:47 ` |WARNING| " dpdklab
2025-02-27 21:00 ` dpdklab
2025-02-27 21:13 ` |FAILURE| " dpdklab
2025-02-27 21:40 ` dpdklab
2025-02-27 21:41 ` dpdklab
2025-02-27 22:21 ` dpdklab
2025-02-28  6:14 ` dpdklab
2025-02-28 15:26 ` |WARNING| " dpdklab
2025-03-01 19:38 ` dpdklab [this message]
2025-03-02  0:07 ` |FAILURE| " dpdklab
2025-03-02  0:10 ` 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=67c36227.050a0220.1c58ab.166aSMTPIN_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).