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| pw137542 [PATCH v4 22/22] devtools: forbid use argument variadic pack extension
Date: Thu, 29 Feb 2024 16:44:44 -0500	[thread overview]
Message-ID: <20240229214444.1913039-1-robot@bytheb.org> (raw)
In-Reply-To: <1709236433-15428-23-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8102416043
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
####################################################################################
../lib/eal/windows/include/rte_windows.h:52:3: error: expected identifier or ‘(’ before string constant
   52 |   "GetLastError()=%lu: " GetLastError(), __VA_ARGS__)
      |   ^~~~~~~~~~~~~~~~~~~~~~
../lib/eal/windows/include/rte_windows.h:52:42: error: __VA_ARGS__ can only appear in the expansion of a C99 variadic macro [-Werror]
   52 |   "GetLastError()=%lu: " GetLastError(), __VA_ARGS__)
      |                                          ^
In file included from ../lib/eal/common/eal_internal_cfg.h:14,
                 from ../lib/eal/common/eal_private.h:18,
                 from ../lib/eal/common/eal_common_class.c:12:
../lib/eal/windows/include/rte_os_shim.h: In function ‘rte_clock_gettime’:
../lib/eal/windows/include/rte_os_shim.h:76:32: error: implicit declaration of function ‘rte_timespec_get’; did you mean ‘timespec_get’? [-Werror=implicit-function-declaration]
   76 | #define timespec_get(ts, base) rte_timespec_get(ts, base)
      |                                ^~~~~~~~~~~~~~~~
../lib/eal/windows/include/rte_os_shim.h:96:7: note: in expansion of macro ‘timespec_get’
   96 |   if (timespec_get(tp, TIME_UTC) != TIME_UTC)
      |       ^~~~~~~~~~~~
../lib/eal/windows/include/rte_os_shim.h:76:32: error: nested extern declaration of ‘rte_timespec_get’ [-Werror=nested-externs]
   76 | #define timespec_get(ts, base) rte_timespec_get(ts, base)
      |                                ^~~~~~~~~~~~~~~~
../lib/eal/windows/include/rte_os_shim.h:96:7: note: in expansion of macro ‘timespec_get’
   96 |   if (timespec_get(tp, TIME_UTC) != TIME_UTC)
      |       ^~~~~~~~~~~~
cc1: all warnings being treated as errors
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-02-29 21:44 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709236433-15428-23-git-send-email-roretzla@linux.microsoft.com>
2024-02-29 19:34 ` |SUCCESS| pw137526-137542 " qemudev
2024-02-29 19:39 ` qemudev
2024-02-29 19:57 ` |SUCCESS| pw137542 " checkpatch
2024-02-29 21:44 ` 0-day Robot [this message]
2024-02-29 22:20 ` |SUCCESS| pw137526-137542 [PATCH] [v4,22/22] devtools: forbid use ar dpdklab
2024-02-29 22:26 ` dpdklab
2024-02-29 22:30 ` dpdklab
2024-02-29 22:31 ` dpdklab
2024-02-29 22:34 ` dpdklab
2024-02-29 22:35 ` dpdklab
2024-02-29 22:37 ` dpdklab
2024-02-29 22:40 ` dpdklab
2024-02-29 23:21 ` dpdklab
2024-02-29 23:22 ` dpdklab
2024-02-29 23:22 ` dpdklab
2024-02-29 23:32 ` dpdklab
2024-02-29 23:34 ` dpdklab
2024-02-29 23:35 ` dpdklab
2024-02-29 23:35 ` dpdklab
2024-02-29 23:35 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-03-01  2:16 ` dpdklab
2024-03-01  2:16 ` dpdklab
2024-03-01  2:17 ` dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:19 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01  2:21 ` |FAILURE| " dpdklab
2024-03-01  2:21 ` |SUCCESS| " dpdklab
2024-03-01  2:21 ` dpdklab
2024-03-01  2:21 ` dpdklab
2024-03-01  2:22 ` |FAILURE| " dpdklab
2024-03-01  2:22 ` |SUCCESS| " dpdklab
2024-03-01  2:22 ` |FAILURE| " dpdklab
2024-03-01  2:22 ` dpdklab
2024-03-01  2:22 ` |SUCCESS| " dpdklab
2024-03-01  2:23 ` |FAILURE| " dpdklab
2024-03-01  2:23 ` dpdklab
2024-03-01  2:23 ` |SUCCESS| " dpdklab
2024-03-01  2:27 ` |FAILURE| " dpdklab
2024-03-01  2:28 ` |SUCCESS| " dpdklab
2024-03-01  2:28 ` dpdklab
2024-03-01  2:32 ` dpdklab
2024-03-01  2:36 ` dpdklab
2024-03-01  2:36 ` dpdklab
2024-03-01  2:45 ` dpdklab
2024-03-01  2:46 ` dpdklab
2024-03-01  2:47 ` dpdklab
2024-03-01  2:47 ` dpdklab
2024-03-01  2:48 ` |FAILURE| " dpdklab
2024-03-01  2:49 ` |SUCCESS| " dpdklab
2024-03-01  2:50 ` dpdklab
2024-03-01  2:50 ` dpdklab
2024-03-01  2:55 ` dpdklab
2024-03-01  3:07 ` dpdklab
2024-03-01  3:13 ` dpdklab
2024-03-01  3:29 ` |FAILURE| " dpdklab
2024-03-01  3:45 ` |SUCCESS| " dpdklab
2024-03-01  3:49 ` dpdklab
2024-03-01  8:09 ` |FAILURE| " dpdklab
2024-03-01 12:13 ` |SUCCESS| " dpdklab
2024-03-01 12:17 ` dpdklab
2024-03-01 12:22 ` dpdklab
2024-03-01 12:27 ` dpdklab
2024-03-02 12:54 ` dpdklab
2024-03-04  1:54 ` dpdklab
2024-03-04  2:26 ` dpdklab
2024-03-04  2:59 ` 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=20240229214444.1913039-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).