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| pw158029-158036 [PATCH] [v4,8/8] doc: update documentation
Date: Thu, 23 Oct 2025 09:10:21 -0700 (PDT)	[thread overview]
Message-ID: <68fa536d.530a0220.239080.6e1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251023154748.38535-9-stephen@networkplumber.org>

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, October 23 2025 15:46:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7c744b9a08cf3dd6bdd215689bb6d2beb8a8a4ef

158029-158036 --> testing issues

Upstream job id: ACVP-FIPS-testing#11534

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): ====
|                    ^~~~~~~
cc1: all warnings being treated as errors
[552/3622] Compiling C object lib/librte_table.a.p/table_rte_table_lpm_ipv6.c.o
[553/3622] Compiling C object lib/librte_table.a.p/table_rte_table_lpm.c.o
[554/3622] Generating symbol file lib/librte_fib.so.26.0.p/librte_fib.so.26.0.symbols
[555/3622] Generating port.sym_chk with a custom command (wrapped by meson to capture output)
[556/3622] Compiling C object lib/librte_table.a.p/table_rte_table_hash_ext.c.o
[557/3622] Compiling C object lib/librte_table.a.p/table_rte_table_hash_key16.c.o
[558/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_port_in_action.c.o
[559/3622] Compiling C object lib/librte_table.a.p/table_rte_table_hash_key32.c.o
[560/3622] Compiling C object lib/librte_table.a.p/table_rte_table_hash_lru.c.o
[561/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_pipeline.c.o
[562/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_ipsec.c.o
[563/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_ctl.c.o
[564/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline_spec.c.o
[565/3622] Compiling C object lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
[566/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline.c.o
[567/3622] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
[568/3622] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

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/34362/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-23 16:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251023154748.38535-9-stephen@networkplumber.org>
2025-10-23 15:13 ` |SUCCESS| pw158029-158036 [PATCH v4 8/8] doc: update documentation on pdump library qemudev
2025-10-23 15:18 ` qemudev
2025-10-23 15:48 ` |SUCCESS| pw158036 " checkpatch
2025-10-23 16:09 ` |FAILURE| pw158029-158036 [PATCH] [v4,8/8] doc: update documentation dpdklab
2025-10-23 16:10 ` dpdklab [this message]
2025-10-23 16:13 ` dpdklab
2025-10-23 16:13 ` |SUCCESS| " dpdklab
2025-10-23 16:18 ` dpdklab
2025-10-23 16:24 ` |FAILURE| " dpdklab
2025-10-23 16:25 ` |PENDING| " dpdklab
2025-10-23 16:30 ` |SUCCESS| " dpdklab
2025-10-23 16:33 ` dpdklab
2025-10-23 16:35 ` dpdklab
2025-10-23 16:35 ` dpdklab
2025-10-23 16:40 ` |WARNING| " dpdklab
2025-10-23 16:42 ` |FAILURE| " dpdklab
2025-10-23 16:45 ` dpdklab
2025-10-23 16:45 ` |WARNING| " dpdklab
2025-10-23 16:51 ` dpdklab
2025-10-23 17:02 ` |SUCCESS| " dpdklab
2025-10-23 17:27 ` dpdklab
2025-10-23 21:10 ` |FAILURE| " 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=68fa536d.530a0220.239080.6e1fSMTPIN_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).