From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Sunil Kumar Kori <skori@marvell.com>,
dpdk-test-reports@iol.unh.edu,
Sunil Kumar Kori <skori@marvell.com>
Subject: |WARNING| pw131265 [PATCH] [v3,1/1] app/graph: add example for diffe
Date: Fri, 08 Sep 2023 07:59:30 -0700 (PDT) [thread overview]
Message-ID: <64fb36d2.4a0a0220.772ec.865fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: WARNING
http://dpdk.org/patch/131265
_Testing issues_
Submitter: Sunil Kumar Kori <skori@marvell.com>
Date: Friday, September 08 2023 10:49:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131265 --> testing fail
Test environment and result as below:
+-----------------+------------------------------+---------------------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+=================+==============================+===========================+
| Debian 11 (arm) | FAIL | FAIL |
+-----------------+------------------------------+---------------------------+
==== 20 line log output for Debian 11 (arm) (cryptodev_sw_zuc_autotest): ====
../app/graph/l3fwd.c:58:30: error: comparison is always true due to limited range of data type [-Werror=type-limits]
58 | for (lcore_id = 0; lcore_id < RTE_MAX_LCORE; lcore_id++) {
| ^
In file included from ../lib/eal/include/generic/rte_spinlock.h:20,
from ../lib/eal/arm/include/rte_spinlock.h:17,
from ../lib/eal/include/generic/rte_power_intrinsics.h:11,
from ../lib/eal/arm/include/rte_power_intrinsics.h:14,
from ../lib/ethdev/rte_ethdev.h:173,
from ../app/graph/l3fwd.c:13:
../lib/eal/include/rte_lcore.h:227:9: error: comparison is always true due to limited range of data type [-Werror=type-limits]
227 | i < RTE_MAX_LCORE; \
| ^
../app/graph/l3fwd.c:123:2: note: in expansion of macro 'RTE_LCORE_FOREACH_WORKER'
123 | RTE_LCORE_FOREACH_WORKER(lcore_id) {
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[2806/3042] Compiling C object 'app/a172ced@@dpdk-test-mldev@exe/test-mldev_parser.c.o'.
[2807/3042] Compiling C object 'app/a172ced@@dpdk-test-mldev@exe/test-mldev_ml_main.c.o'.
[2808/3042] Generating rte_event_cnxk.pmd.c with a custom command.
ninja: build stopped: subcommand failed.
==== End log output ====
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27558/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-08 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-08 16:29 dpdklab
2023-09-08 14: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=64fb36d2.4a0a0220.772ec.865fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=skori@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).