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| pw152125 [PATCH] net/mlx5: fix LACP packets handling in is
Date: Sat, 01 Mar 2025 19:00:13 -0800 (PST)	[thread overview]
Message-ID: <67c3c9bd.050a0220.50eba.8199SMTPIN_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#9101

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
[2164/3181] Compiling C object drivers/net/thunderx/base/libnicvf_base.a.p/nicvf_bsvf.c.o
[2165/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_dcb_hw.c.o
[2166/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_eeprom.c.o
[2167/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_dcb.c.o
[2168/3181] Generating rte_net_softnic.pmd.c with a custom command
[2169/3181] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_flow.c.o
[2170/3181] Generating rte_net_sfc.pmd.c with a custom command
[2171/3181] Compiling C object drivers/net/thunderx/base/libnicvf_base.a.p/nicvf_hw.c.o
[2172/3181] Compiling C object drivers/net/thunderx/base/libnicvf_base.a.p/nicvf_mbox.c.o
[2173/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_mbx.c.o
[2174/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_mng.c.o
[2175/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_vf.c.o
[2176/3181] Compiling C object drivers/libtmp_rte_net_thunderx.a.p/net_thunderx_nicvf_rxtx.c.o
[2177/3181] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_rte_eth_tap.c.o
[2178/3181] Compiling C object drivers/libtmp_rte_net_thunderx.a.p/net_thunderx_nicvf_ethdev.c.o
[2179/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_phy.c.o
[2180/3181] Compiling C object drivers/net/txgbe/base/libtxgbe_base.a.p/txgbe_hw.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/32704/

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-02  3:00 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
2025-03-02  2:51 ` |FAILURE| " dpdklab
2025-03-02  2:54 ` dpdklab
2025-03-02  3:00 ` dpdklab [this message]
2025-03-02  3:19 ` 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=67c3c9bd.050a0220.50eba.8199SMTPIN_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).