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| pw150556-150559 [PATCH] [4/4] net/netvsc: cache device par
Date: Tue, 28 Jan 2025 05:48:59 -0800 (PST)	[thread overview]
Message-ID: <6798e04b.050a0220.38fc65.e11aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1738028106-25239-4-git-send-email-longli@linuxonhyperv.com>

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

_Testing issues_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tuesday, January 28 2025 01:35:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3ba602522abfc4db664008b89ec7c90cfbf7173d

150556-150559 --> testing issues

Upstream job id: ACVP-FIPS-testing#8705

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
[1832/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_hws_mlx5dr_bwc.c.o
[1833/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_hws_mlx5dr_action.c.o
[1834/3169] Compiling C object drivers/libtmp_rte_net_netvsc.a.p/net_netvsc_hn_rndis.c.o
[1835/3169] Compiling C object drivers/libtmp_rte_net_netvsc.a.p/net_netvsc_hn_vf.c.o
[1836/3169] Compiling C object drivers/net/nfp/libnfp_avx2_lib.a.p/nfp_rxtx_vec_avx2.c.o
[1837/3169] Compiling C object drivers/net/nfp/libnfp_avx2_lib.a.p/nfdk_nfp_nfdk_vec_avx2_dp.c.o
[1838/3169] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1839/3169] Compiling C object drivers/libtmp_rte_net_nfp.a.p/net_nfp_flower_nfp_flower.c.o
[1840/3169] Compiling C object drivers/libtmp_rte_net_netvsc.a.p/net_netvsc_hn_rxtx.c.o
[1841/3169] Compiling C object drivers/libtmp_rte_net_nfp.a.p/net_nfp_flower_nfp_flower_cmsg.c.o
[1842/3169] Compiling C object drivers/libtmp_rte_net_nfp.a.p/net_nfp_flower_nfp_conntrack.c.o
[1843/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_hws_mlx5dr_definer.c.o
[1844/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_dv.c.o
[1845/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.o
[1846/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.o
[1847/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.o
[1848/3169] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_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/32437/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-01-28 13:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1738028106-25239-4-git-send-email-longli@linuxonhyperv.com>
2025-01-28  1:14 ` |SUCCESS| pw150556-150559 [PATCH 4/4] net/netvsc: cache device parameters for hot plug events qemudev
2025-01-28  1:18 ` qemudev
2025-01-28  1:34 ` |SUCCESS| pw150559 " checkpatch
2025-01-28  2:23 ` |FAILURE| " 0-day Robot
2025-01-28  2:30 ` |PENDING| pw150556-150559 [PATCH] [4/4] net/netvsc: cache device par dpdklab
2025-01-28  2:31 ` |SUCCESS| " dpdklab
2025-01-28  2:33 ` |PENDING| " dpdklab
2025-01-28  2:33 ` |SUCCESS| " dpdklab
2025-01-28  2:35 ` dpdklab
2025-01-28  2:36 ` |FAILURE| " dpdklab
2025-01-28  2:37 ` dpdklab
2025-01-28  2:38 ` |SUCCESS| " dpdklab
2025-01-28  2:41 ` |FAILURE| " dpdklab
2025-01-28  2:41 ` dpdklab
2025-01-28  2:43 ` |SUCCESS| " dpdklab
2025-01-28  2:45 ` dpdklab
2025-01-28  2:49 ` |FAILURE| " dpdklab
2025-01-28  2:51 ` dpdklab
2025-01-28  2:52 ` dpdklab
2025-01-28  2:53 ` dpdklab
2025-01-28  2:55 ` dpdklab
2025-01-28  2:55 ` dpdklab
2025-01-28  2:57 ` dpdklab
2025-01-28  2:59 ` |SUCCESS| " dpdklab
2025-01-28  3:01 ` |FAILURE| " dpdklab
2025-01-28  3:03 ` dpdklab
2025-01-28  3:06 ` dpdklab
2025-01-28  3:09 ` |WARNING| " dpdklab
2025-01-28  3:16 ` |FAILURE| " dpdklab
2025-01-28  3:22 ` |SUCCESS| " dpdklab
2025-01-28  3:49 ` |WARNING| " dpdklab
2025-01-28  3:49 ` |FAILURE| " dpdklab
2025-01-28 13:48 ` dpdklab [this message]
2025-01-30  1:54 ` |SUCCESS| " 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=6798e04b.050a0220.38fc65.e11aSMTPIN_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).