From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: anoobj@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw114813 [PATCH 1/1] app/test-security-perf: add security perf app
Date: Thu, 11 Aug 2022 01:19:30 -0400 [thread overview]
Message-ID: <20220811051930.29302-1-robot@bytheb.org> (raw)
In-Reply-To: <20220811035933.802-2-anoobj@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/114813/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2837365020
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-static-i386" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-static-i386" at step Build and test
####################################################################################
from ../lib/cryptodev/rte_crypto.h:20,
from ../lib/cryptodev/rte_cryptodev.h:22,
from ../app/test-security-perf/test_security_perf.c:10:
../app/test-security-perf/test_security_perf.c: In function ‘cryptodev_init’:
../app/test-security-perf/test_security_perf.c:116:6: error: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 4 has type ‘long unsigned int’ [-Werror=format=]
116 | i);
| ~^
| |
| long unsigned int
../lib/eal/include/rte_log.h:342:25: note: in definition of macro ‘RTE_LOG’
342 | RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
| ^
../app/test-security-perf/test_security_perf.c:129:31: error: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 4 has type ‘long unsigned int’ [-Werror=format=]
129 | " %" PRIu64 " - %d", i, j);
| ~ ^
| |
| long unsigned int
../lib/eal/include/rte_log.h:342:25: note: in definition of macro ‘RTE_LOG’
342 | RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
| ^
cc1: all warnings being treated as errors
[1953/3112] Compiling C object 'app/a172ced@@dpdk-test-security-perf@exe/test_test_cryptodev_security_ipsec.c.o'.
[1954/3112] Linking target app/dpdk-test-regex.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-static-i386" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2022-08-11 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220811035933.802-2-anoobj@marvell.com>
2022-08-11 4:01 ` |WARNING| " checkpatch
2022-08-11 5:19 ` 0-day Robot [this message]
2022-08-16 0:32 |FAILURE| pw114813 [PATCH] [1/1] " 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=20220811051930.29302-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=anoobj@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).