From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: gmuthukrishn@marvell.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw96505 [dpdk-dev] [v2, 3/3] common/cnxk: add telemetry endpoints to npa
Date: Sun, 1 Aug 2021 14:18:21 -0400 [thread overview]
Message-ID: <20210801181821.24149-1-robot@bytheb.org> (raw)
In-Reply-To: <89b4c9fa2f40b8127629754e2ef7575db39d725a.1627839051.git.gmuthukrishn@marvell.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=pw|patchwork.dpdk.org|build|18120|SHA|730fdf015e5a4fe5aa5308aaf69230c18b1d40be|passed|https://github.com/ovsrobot/dpdk/actions/runs/1087831825|[dpdk-dev] [PATCH] app/test: quieten noise while forking|ovsrobot/dpdk, Size: 2794 bytes --]
From: robot@bytheb.org
Test-Label: github-robot
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/96505/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1087830803
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-18.04-gcc-static-i386" failed at step "Build and test"
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-18.04-gcc-static-i386" at step "Build and test"
####################################################################################
return __json_snprintf(buf, len, "[%ld]", (uintptr_t)ptr);
~~^ ~~~~~~~~~~~~~~
%d
../lib/telemetry/telemetry_json.h:114:50: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘unsigned int’ [-Werror=format=]
ret = __json_snprintf(buf + end, len - end, ",%ld]", (uintptr_t)ptr);
~~^ ~~~~~~~~~~~~~~
%d
../lib/telemetry/telemetry_json.h: In function ‘rte_tel_json_add_obj_ptr’:
../lib/telemetry/telemetry_json.h:162:47: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘unsigned int’ [-Werror=format=]
return __json_snprintf(buf, len, "{\"%s\":%ld}", name,
~~^
%d
(uintptr_t)ptr);
~~~~~~~~~~~~~~
../lib/telemetry/telemetry_json.h:165:57: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘unsigned int’ [-Werror=format=]
ret = __json_snprintf(buf + end, len - end, ",\"%s\":%ld}", name,
~~^
%d
(uintptr_t)ptr);
~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[8/2510] Generating symbol file 'lib/76b5a35@@rte_kvargs@sha/librte_kvargs.so.21.3.symbols'.
[9/2510] Compiling C object 'lib/76b5a35@@rte_telemetry@sta/telemetry_telemetry_legacy.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-18.04-gcc-static-i386" at step "Build and test"
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2021-08-01 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89b4c9fa2f40b8127629754e2ef7575db39d725a.1627839051.git.gmuthukrishn@marvell.com>
2021-08-01 17:38 ` [dpdk-test-report] |SUCCESS| pw96505 " checkpatch
2021-08-01 18:18 ` 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=20210801181821.24149-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=gmuthukrishn@marvell.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).