automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: andremue@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw150588 [PATCH v2 2/2] stack: enable build with MSVC
Date: Tue, 28 Jan 2025 17:03:51 -0500	[thread overview]
Message-ID: <20250128220351.2810524-1-robot@bytheb.org> (raw)
In-Reply-To: <1738099014-16629-3-git-send-email-andremue@linux.microsoft.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13019847832
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-shared-aarch64" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-shared-aarch64" at step Build and test
####################################################################################
ccache aarch64-linux-gnu-gcc -Ilib/librte_stack.a.p -Ilib -I../lib -Ilib/stack -I../lib/stack -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/arm/include -I../lib/eal/arm/include -I../kernel/linux -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=armv8-a+crc -moutline-atomics -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.stack -MD -MQ lib/librte_stack.a.p/stack_rte_stack.c.o -MF lib/librte_stack.a.p/stack_rte_stack.c.o.d -o lib/librte_stack.a.p/stack_rte_stack.c.o -c ../lib/stack/rte_stack.c
In file included from ../lib/stack/rte_stack_lf.h:12,
                 from ../lib/stack/rte_stack.h:92,
                 from ../lib/stack/rte_stack.c:16:
../lib/stack/rte_stack_lf_c11.h: In function ‘__rte_atomic128_cmp_exchange’:
../lib/stack/rte_stack_lf_c11.h:51:23: error: expected string literal before ‘MPLOCKED’
   51 |                       MPLOCKED
      |                       ^~~~~~~~
../lib/stack/rte_stack_lf_c11.h:38:44: error: unused parameter ‘dst’ [-Werror=unused-parameter]
   38 | __rte_atomic128_cmp_exchange(rte_int128_t *dst,
      |                              ~~~~~~~~~~~~~~^~~
../lib/stack/rte_stack_lf_c11.h:39:44: error: unused parameter ‘exp’ [-Werror=unused-parameter]
   39 |                              rte_int128_t *exp,
      |                              ~~~~~~~~~~~~~~^~~
../lib/stack/rte_stack_lf_c11.h:40:50: error: unused parameter ‘src’ [-Werror=unused-parameter]
   40 |                              const rte_int128_t *src,
      |                              ~~~~~~~~~~~~~~~~~~~~^~~
cc1: all warnings being treated as errors
[392/6623] Generating reorder.sym_chk with a custom command (wrapped by meson to capture output)
[393/6623] Generating rib.sym_chk with a custom command (wrapped by meson to capture output)
[394/6623] Compiling C object lib/librte_security.a.p/security_rte_security.c.o
[395/6623] Compiling C object lib/librte_sched.a.p/sched_rte_sched.c.o
[396/6623] Generating mldev.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-shared-aarch64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-01-28 22:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1738099014-16629-3-git-send-email-andremue@linux.microsoft.com>
2025-01-28 20:43 ` |SUCCESS| pw150587-150588 " qemudev
2025-01-28 20:47 ` qemudev
2025-01-28 21:17 ` |SUCCESS| pw150588 " checkpatch
2025-01-28 21:48 ` |FAILURE| pw150587-150588 [PATCH] [v2,2/2] stack: enable build with dpdklab
2025-01-28 21:53 ` dpdklab
2025-01-28 21:57 ` dpdklab
2025-01-28 22:00 ` |PENDING| " dpdklab
2025-01-28 22:02 ` |SUCCESS| " dpdklab
2025-01-28 22:03 ` 0-day Robot [this message]
2025-01-28 22:06 ` |WARNING| " dpdklab
2025-01-28 22:08 ` |SUCCESS| " dpdklab
2025-01-28 22:10 ` dpdklab
2025-01-28 22:13 ` dpdklab
2025-01-28 22:14 ` |PENDING| " dpdklab
2025-01-28 22:26 ` dpdklab
2025-01-28 22:35 ` |FAILURE| " dpdklab
2025-01-28 22:40 ` dpdklab
2025-01-28 22:55 ` |SUCCESS| " dpdklab
2025-01-28 23:06 ` |WARNING| " dpdklab
2025-01-28 23:10 ` |SUCCESS| " dpdklab
2025-01-30  2:17 ` 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=20250128220351.2810524-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=andremue@linux.microsoft.com \
    --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).