automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: roretzla@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw134940 [PATCH] eal: initialize shared plugins on Windows
Date: Thu,  7 Dec 2023 15:20:47 -0500	[thread overview]
Message-ID: <20231207202047.577183-1-robot@bytheb.org> (raw)
In-Reply-To: <1701976851-17275-2-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-static-mingw" at step Build and test
####################################################################################
  445 |    RTE_LOG(ERR, EAL, "Error loading %s, error code: %" PRIu32 "\n",
      |                                                        ^~~~~~
../lib/log/rte_log.h:333:32: note: in definition of macro ‘RTE_LOG’
  333 |    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
      |                                ^~~~~~~~~~~
../lib/eal/common/eal_common_options.c:446:32: error: format ‘%s’ expects a matching ‘char *’ argument [-Werror=format=]
  446 |        loadpath, GetLastError());
      |                                ^
../lib/log/rte_log.h:333:25: note: in definition of macro ‘RTE_LOG’
  333 |    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
      |                         ^
../lib/eal/common/eal_common_options.c:446:32: error: spurious trailing ‘%’ in format [-Werror=format=]
  446 |        loadpath, GetLastError());
      |                                ^
../lib/log/rte_log.h:333:25: note: in definition of macro ‘RTE_LOG’
  333 |    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
      |                         ^
cc1: all warnings being treated as errors
[45/1439] Generating symbol file 'lib/76b5a35@@rte_kvargs@sha/librte_kvargs-24.dll.symbols'.
[46/1439] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_malloc.c.obj'.
[47/1439] Generating symbol file 'lib/76b5a35@@rte_telemetry@sha/librte_telemetry-24.dll.symbols'.
[48/1439] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_rte_service.c.obj'.
[49/1439] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_dynmem.c.obj'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-static-mingw" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

      parent reply	other threads:[~2023-12-07 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1701976851-17275-2-git-send-email-roretzla@linux.microsoft.com>
2023-12-07 19:11 ` |SUCCESS| " qemudev
2023-12-07 19:15 ` qemudev
2023-12-07 19:21 ` checkpatch
2023-12-07 20:20 ` 0-day Robot [this message]

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=20231207202047.577183-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=roretzla@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).