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| pw144146 [PATCH v22 15/15] doc: add release note about log library
Date: Tue, 17 Sep 2024 17:24:24 -0400	[thread overview]
Message-ID: <20240917212424.2581162-1-robot@bytheb.org> (raw)
In-Reply-To: <20240917203828.414701-16-stephen@networkplumber.org>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
ninja: Entering directory `build'
[1/1469] Generating rte_log_mingw with a custom command.
[2/1469] Generating rte_kvargs_mingw with a custom command.
[3/1469] Compiling C object 'lib/76b5a35@@rte_argparse@sta/argparse_rte_argparse.c.obj'.
[4/1469] Compiling C object 'lib/76b5a35@@rte_log@sta/log_log_color.c.obj'.
[5/1469] Generating rte_argparse_mingw with a custom command.
[6/1469] Compiling C object 'lib/76b5a35@@rte_log@sta/log_log_stubs.c.obj'.
[7/1469] Compiling C object 'lib/76b5a35@@rte_log@sta/log_log_timestamp.c.obj'.
[8/1469] Linking static target lib/librte_argparse.a.
[9/1469] Generating rte_telemetry_mingw with a custom command.
[10/1469] Compiling C object 'lib/76b5a35@@rte_log@sta/log_log.c.obj'.
FAILED: lib/76b5a35@@rte_log@sta/log_log.c.obj 
ccache x86_64-w64-mingw32-gcc -Ilib/76b5a35@@rte_log@sta -Ilib -I../lib -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/log -I../lib/log -fdiagnostics-color=always -pipe -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-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -D_WIN32_WINNT=0x0A00 -D__USE_MINGW_ANSI_STDIO -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.log -MD -MQ 'lib/76b5a35@@rte_log@sta/log_log.c.obj' -MF 'lib/76b5a35@@rte_log@sta/log_log.c.obj.d' -o 'lib/76b5a35@@rte_log@sta/log_log.c.obj' -c ../lib/log/log.c
../lib/log/log.c: In function ‘eal_log_init’:
../lib/log/log.c:540:1: error: label ‘notice’ defined but not used [-Werror=unused-label]
  540 | notice:
      | ^~~~~~
cc1: all warnings being treated as errors
[11/1469] Compiling C object 'lib/76b5a35@@rte_kvargs@sta/kvargs_rte_kvargs.c.obj'.
[12/1469] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry_data.c.obj'.
[13/1469] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry.c.obj'.
[14/1469] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry_legacy.c.obj'.
[15/1469] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_bus.c.obj'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-09-17 21:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240917203828.414701-16-stephen@networkplumber.org>
2024-09-17 20:17 ` |SUCCESS| pw144132-144146 " qemudev
2024-09-17 20:22 ` qemudev
2024-09-17 20:45 ` |SUCCESS| pw144146 " checkpatch
2024-09-17 21:24 ` 0-day Robot [this message]
2024-09-17 23:35 ` |SUCCESS| pw144132-144146 [PATCH] [v22,15/15] doc: add release note dpdklab
2024-09-18  0:38 ` dpdklab
2024-09-18  0:57 ` dpdklab
2024-09-18  1:06 ` dpdklab
2024-09-18  1:33 ` dpdklab
2024-09-18  3:58 ` |FAILURE| " dpdklab
2024-09-18  4:25 ` |PENDING| " dpdklab
2024-09-18  4:36 ` |FAILURE| " dpdklab
2024-09-18  4:39 ` dpdklab
2024-09-18  4:40 ` dpdklab
2024-09-18  5:29 ` |SUCCESS| " dpdklab
2024-09-18  5:46 ` dpdklab
2024-09-18  5:48 ` dpdklab
2024-09-18  6:03 ` |FAILURE| " dpdklab
2024-09-18  6:43 ` dpdklab
2024-09-18 10:38 ` |SUCCESS| " dpdklab
2024-09-18 15:07 ` dpdklab
2024-09-22 10:24 ` dpdklab
2024-09-22 10:36 ` 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=20240917212424.2581162-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).