automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw156139 [PATCH v2 43/43] eal: remove no longer used windows version of sys/queue.h
Date: Mon, 25 Aug 2025 01:05:27 -0400	[thread overview]
Message-ID: <20250825050527.3279929-1-robot@bytheb.org> (raw)
In-Reply-To: <20250825034126.12046-44-stephen@networkplumber.org>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/156139/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/17198793355
Build Logs:
-----------------------Summary of failed steps-----------------------
"windows-2022-msvc" failed at step Build
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "windows-2022-msvc" at step Build
####################################################################################
[67/452] Compiling C object lib/librte_eal.a.p/eal_x86_rte_cycles.c.obj
[68/452] Compiling C object lib/librte_eal.a.p/eal_x86_rte_power_intrinsics.c.obj
[69/452] Linking target lib/rte_telemetry-26.dll
   Creating library lib\rte_telemetry.lib and object lib\rte_telemetry.exp
[70/452] Generating lib/rte_eal_map with a custom command
[71/452] Generating lib/rte_ring_map with a custom command
[72/452] Compiling C object lib/librte_eal.a.p/eal_x86_rte_mmu.c.obj
[73/452] Compiling C object lib/librte_ring.a.p/ring_rte_ring.c.obj
[74/452] Compiling C object lib/librte_ring.a.p/ring_rte_soring.c.obj
[75/452] Compiling C object lib/librte_mempool.a.p/mempool_rte_mempool.c.obj
FAILED: [code=2] lib/librte_mempool.a.p/mempool_rte_mempool.c.obj 
"cl" "-Ilib\librte_mempool.a.p" "-Ilib" "-I..\lib" "-Ilib\mempool" "-I..\lib\mempool" "-Ilib\eal\common" "-I..\lib\eal\common" "-I." "-I.." "-Iconfig" "-I..\config" "-Ilib\eal\include" "-I..\lib\eal\include" "-Ilib\eal\windows\include" "-I..\lib\eal\windows\include" "-Ilib\eal\x86\include" "-I..\lib\eal\x86\include" "-Ilib\eal" "-I..\lib\eal" "-Ilib\log" "-I..\lib\log" "-Ilib\kvargs" "-I..\lib\kvargs" "-Ilib\ring" "-I..\lib\ring" "-Ilib\metrics" "-I..\lib\metrics" "-Ilib\telemetry" "-I..\lib\telemetry" "/MD" "/nologo" "/showIncludes" "/utf-8" "/W3" "/WX" "/std:c11" "/O2" "/Gw" "/wd4244" "/wd4267" "/wd4146" "/experimental:c11atomics" "/d1experimental:typeof" "/experimental:statementExpressions" "/FI" "rte_config.h" "-D_GNU_SOURCE" "-D_WIN32_WINNT=0x0A00" "-DALLOW_EXPERIMENTAL_API" "-DALLOW_INTERNAL_API" "-DRTE_LOG_DEFAULT_LOGTYPE=lib.mempool" "/Fdlib\librte_mempool.a.p\mempool_rte_mempool.c.pdb" /Folib/librte_mempool.a.p/mempool_rte_mempool.c.obj "/c" ../lib/mempool/rte_mempool.c
../lib/mempool/rte_mempool.c(284): error C7714: the syntax for a 'statement-expression' is '__extension__ ({ S1; ... ; Sn; })'
../lib/mempool/rte_mempool.c(291): error C7714: the syntax for a 'statement-expression' is '__extension__ ({ S1; ... ; Sn; })'
../lib/mempool/rte_mempool.c(679): error C7714: the syntax for a 'statement-expression' is '__extension__ ({ S1; ... ; Sn; })'
[76/452] Linking target lib/rte_eal-26.dll
   Creating library lib\rte_eal.lib and object lib\rte_eal.exp
[77/452] Compiling C object lib/librte_ring.a.p/ring_soring.c.obj
[78/452] Generating symbol file lib/rte_telemetry-26.dll.p/rte_telemetry-26.dll.symbols
[79/452] Compiling C object lib/librte_mempool.a.p/mempool_rte_mempool_ops.c.obj
[80/452] Compiling C object lib/librte_mempool.a.p/mempool_rte_mempool_ops_default.c.obj
ninja: build stopped: subcommand failed.
INFO: autodetecting backend as ninja
INFO: calculating backend command to run: C:\hostedtoolcache\windows\Python\3.13.7\x64\Scripts\ninja.EXE -C D:/a/dpdk/dpdk/build
##[error]Process completed with exit code 2.
####################################################################################
#### [End job log] "windows-2022-msvc" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-08-25  5:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250825034126.12046-44-stephen@networkplumber.org>
2025-08-25  3:13 ` |SUCCESS| pw156097-156139 " qemudev
2025-08-25  3:18 ` qemudev
2025-08-25  3:44 ` |SUCCESS| pw156139 " checkpatch
2025-08-25  5:05 ` 0-day Robot [this message]
2025-08-25 17:28 ` |FAILURE| pw156097-156139 [PATCH] [v2,43/43] eal: remove no longer u dpdklab
2025-08-25 17:30 ` |SUCCESS| " dpdklab
2025-08-25 17:33 ` dpdklab
2025-08-25 17:48 ` |FAILURE| " dpdklab
2025-08-25 18:17 ` |SUCCESS| " dpdklab
2025-08-25 18:46 ` |PENDING| " dpdklab
2025-08-25 19:13 ` |SUCCESS| " dpdklab
2025-08-25 19:21 ` |PENDING| " dpdklab
2025-08-25 19:28 ` |FAILURE| " dpdklab
2025-08-25 19:36 ` |SUCCESS| " dpdklab
2025-08-25 20:22 ` |FAILURE| " dpdklab
2025-08-25 20:39 ` dpdklab
2025-08-25 21:19 ` |SUCCESS| " dpdklab
2025-08-25 21:20 ` dpdklab
2025-08-25 21:23 ` |PENDING| " dpdklab
2025-08-25 21:42 ` |WARNING| " 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=20250825050527.3279929-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).