From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw129124 [PATCH v6 6/6] eal: add option to put timestamp on console output
Date: Thu, 29 Jun 2023 13:19:18 -0400 [thread overview]
Message-ID: <20230629171918.569078-1-robot@bytheb.org> (raw)
In-Reply-To: <20230629155858.75668-7-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/129124/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5414510891
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
####################################################################################
In file included from ../lib/eal/common/eal_common_log.c:5:
../lib/eal/common/eal_common_log.c: In function ‘eal_log_level_parse’:
../lib/eal/windows/include/getopt.h:38:16: error: initialization discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
38 | #define optarg usual_optarg
| ^~~~~~~~~~~~
../lib/eal/common/eal_common_log.c:239:28: note: in expansion of macro ‘optarg’
239 | char * const old_optarg = optarg;
| ^~~~~~
../lib/eal/common/eal_common_log.c:248:34: error: passing argument 2 of ‘usual_getopt_long’ discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
248 | while ((opt = getopt_long(argc, argv, eal_short_options,
| ^~~~
../lib/eal/windows/include/getopt.h:43:57: note: in definition of macro ‘getopt_long’
43 | #define getopt_long(a, b, c, d, e) usual_getopt_long(a, b, c, d, e)
| ^
../lib/eal/windows/include/getopt.h:86:33: note: expected ‘char **’ but argument is of type ‘char * const*’
86 | int getopt_long(int argc, char *argv[], const char *options,
| ~~~~~~^~~~~~
../lib/eal/windows/include/getopt.h:43:57: note: in definition of macro ‘getopt_long’
43 | #define getopt_long(a, b, c, d, e) usual_getopt_long(a, b, c, d, e)
| ^
cc1: all warnings being treated as errors
[25/1426] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_lcore.c.obj'.
[26/1426] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_common_eal_common_mcfg.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-----------------------------
prev parent reply other threads:[~2023-06-29 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230629155858.75668-7-stephen@networkplumber.org>
2023-06-29 15:51 ` |SUCCESS| pw129119-129124 " qemudev
2023-06-29 15:55 ` qemudev
2023-06-29 16:01 ` |SUCCESS| pw129124 " checkpatch
2023-06-29 17:19 ` 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=20230629171918.569078-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).