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: |FAILURE| pw158029-158036 [PATCH] [v4,8/8] doc: update documentation
Date: Thu, 23 Oct 2025 09:09:24 -0700 (PDT)	[thread overview]
Message-ID: <68fa5334.050a0220.100c40.263bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251023154748.38535-9-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
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: Generic-VM-DPDK-Compile-Meson#39208

Test environment and result as below:

+---------------------+--------------------+-------------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_llvm_clang_compile | dpdk_msvc_compile |
+=====================+====================+=========================+===================+
| Ubuntu 20.04        | FAIL               | SKIPPED                 | SKIPPED           |
+---------------------+--------------------+-------------------------+-------------------+
| FreeBSD 14.2        | PEND               | SKIPPED                 | SKIPPED           |
+---------------------+--------------------+-------------------------+-------------------+
| Windows Server 2022 | SKIPPED            | PEND                    | PEND              |
+---------------------+--------------------+-------------------------+-------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_meson_compile): ====
[590/3591] Generating ipsec.sym_chk with a custom command (wrapped by meson to capture output)
[591/3591] Linking target lib/librte_mldev.so.26.0
[592/3591] Linking target lib/librte_reorder.so.26.0
[593/3591] Generating graph.sym_chk with a custom command (wrapped by meson to capture output)
[594/3591] Generating node.sym_chk with a custom command (wrapped by meson to capture output)
[595/3591] Generating eventdev.sym_chk with a custom command (wrapped by meson to capture output)
[596/3591] Generating symbol file lib/librte_compressdev.so.26.0.p/librte_compressdev.so.26.0.symbols
[597/3591] Generating symbol file lib/librte_bbdev.so.26.0.p/librte_bbdev.so.26.0.symbols
[598/3591] Generating rte_bus_auxiliary.sym_chk with a custom command (wrapped by meson to capture output)
[599/3591] Generating rte_common_ionic.sym_chk with a custom command (wrapped by meson to capture output)
[600/3591] Generating symbol file lib/librte_net.so.26.0.p/librte_net.so.26.0.symbols
[601/3591] Generating rte_common_octeontx.sym_chk with a custom command (wrapped by meson to capture output)
[602/3591] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_ipsec.c.o
[603/3591] Generating symbol file lib/librte_cryptodev.so.26.0.p/librte_cryptodev.so.26.0.symbols
[604/3591] Generating pdcp.sym_chk with a custom command (wrapped by meson to capture output)
[605/3591] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[606/3591] Generating rte_common_dpaax.sym_chk with a custom command (wrapped by meson to capture output)
[607/3591] Compiling C object lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
[608/3591] 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: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

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:09 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 ` dpdklab [this message]
2025-10-23 16:10 ` |WARNING| pw158029-158036 [PATCH] [v4,8/8] doc: update documentation dpdklab
2025-10-23 16:13 ` |FAILURE| " 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=68fa5334.050a0220.100c40.263bSMTPIN_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).