From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: aditya.ambadipudi@arm.com, robot@bytheb.org
Subject: |FAILURE| pw139013 [PATCH v1 2/2] deque: add unit tests for the deque library
Date: Mon, 1 Apr 2024 00:25:30 -0400 [thread overview]
Message-ID: <20240401042530.4173083-1-robot@bytheb.org> (raw)
In-Reply-To: <20240401013729.1466298-3-aditya.ambadipudi@arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/139013/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8503526118
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
| ^~
../app/test/test_deque_enqueue_dequeue.c:38:15: note: in definition of macro ‘TEST_DEQUE_VERIFY’
38 | if (!(exp)) { \
| ^~~
../app/test/test_deque_enqueue_dequeue.c:471:47: error: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Werror=sign-compare]
471 | TEST_DEQUE_VERIFY(ret == (int)dsz, d, goto fail);
| ^~
../app/test/test_deque_enqueue_dequeue.c:38:15: note: in definition of macro ‘TEST_DEQUE_VERIFY’
38 | if (!(exp)) { \
| ^~~
../app/test/test_deque_enqueue_dequeue.c: In function ‘test_deque_stack_random_tests1’:
../app/test/test_deque_enqueue_dequeue.c:977:47: error: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Werror=sign-compare]
977 | TEST_DEQUE_VERIFY(ret == (int)dsz, d, goto fail);
| ^~
../app/test/test_deque_enqueue_dequeue.c:38:15: note: in definition of macro ‘TEST_DEQUE_VERIFY’
38 | if (!(exp)) { \
| ^~~
cc1: all warnings being treated as errors
[2868/4046] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ethdev_api.c.o'.
[2869/4046] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_dispatcher.c.o'.
[2870/4046] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ethdev_link.c.o'.
[2871/4046] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_distributor.c.o'.
[2872/4046] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_cryptodev.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-04-01 4:25 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240401013729.1466298-3-aditya.ambadipudi@arm.com>
2024-04-01 1:14 ` |SUCCESS| pw139012-139013 " qemudev
2024-04-01 1:18 ` qemudev
2024-04-01 1:38 ` |WARNING| pw139013 " checkpatch
2024-04-01 2:17 ` |SUCCESS| pw139012-139013 [PATCH] [v1,2/2] deque: add unit tests for dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:23 ` dpdklab
2024-04-01 2:23 ` dpdklab
2024-04-01 2:24 ` dpdklab
2024-04-01 2:24 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:27 ` dpdklab
2024-04-01 2:27 ` dpdklab
2024-04-01 2:28 ` dpdklab
2024-04-01 2:28 ` dpdklab
2024-04-01 2:29 ` dpdklab
2024-04-01 2:29 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:32 ` dpdklab
2024-04-01 2:32 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:37 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:40 ` dpdklab
2024-04-01 2:40 ` dpdklab
2024-04-01 2:41 ` dpdklab
2024-04-01 2:42 ` dpdklab
2024-04-01 2:44 ` dpdklab
2024-04-01 2:45 ` dpdklab
2024-04-01 2:45 ` dpdklab
2024-04-01 2:47 ` dpdklab
2024-04-01 2:48 ` dpdklab
2024-04-01 2:48 ` dpdklab
2024-04-01 2:53 ` dpdklab
2024-04-01 2:56 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:58 ` dpdklab
2024-04-01 3:02 ` dpdklab
2024-04-01 3:05 ` dpdklab
2024-04-01 3:14 ` dpdklab
2024-04-01 3:32 ` dpdklab
2024-04-01 3:34 ` dpdklab
2024-04-01 4:25 ` 0-day Robot [this message]
2024-04-03 10:10 ` dpdklab
2024-04-03 10:13 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:31 ` dpdklab
2024-04-03 10:35 ` 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=20240401042530.4173083-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=aditya.ambadipudi@arm.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).