From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 820ca9fccac850557967172cd1ffce2359fa08c2
Date: Sat, 26 Nov 2022 06:19:00 +0000 (UTC) [thread overview]
Message-ID: <20221126061900.177EC60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]
_Testing issues_
Branch: tags/v20.11
820ca9fccac850557967172cd1ffce2359fa08c2 --> testing fail
Test environment and result as below:
+-----------------------------+----------+
| Environment | abi_test |
+=============================+==========+
| Ubuntu 20.04 ARM GCC Native | FAIL |
+-----------------------------+----------+
==== 20 line log output for Ubuntu 20.04 ARM GCC Native (abi_test): ====
../examples/vm_power_manager/channel_manager.c:1010:2: warning: nested extern declaration of ‘RTE_TAILQ_FOREACH_SAFE’ [-Wnested-externs]
../examples/vm_power_manager/channel_manager.c:1010:35: error: ‘vm_list_head’ undeclared (first use in this function)
1010 | RTE_TAILQ_FOREACH_SAFE(vm_info, &vm_list_head, vms_info, tmp) {
| ^~~~~~~~~~~~
../examples/vm_power_manager/channel_manager.c:1010:49: error: ‘vms_info’ undeclared (first use in this function); did you mean ‘vm_info’?
1010 | RTE_TAILQ_FOREACH_SAFE(vm_info, &vm_list_head, vms_info, tmp) {
| ^~~~~~~~
| vm_info
../examples/vm_power_manager/channel_manager.c:1010:63: error: expected ‘;’ before ‘{’ token
1010 | RTE_TAILQ_FOREACH_SAFE(vm_info, &vm_list_head, vms_info, tmp) {
| ^~
| ;
../examples/vm_power_manager/channel_manager.c:1007:7: warning: unused variable ‘mask’ [-Wunused-variable]
1007 | char mask[RTE_MAX_LCORE];
| ^~~~
../examples/vm_power_manager/channel_manager.c:1006:11: warning: unused variable ‘i’ [-Wunused-variable]
1006 | unsigned i;
| ^
[2720/2744] Linking target examples/dpdk-vdpa
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/22437/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-11-26 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 6:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-01 0:04 dpdklab
2022-11-30 23:08 dpdklab
2022-11-28 6:05 dpdklab
2022-11-27 6:15 dpdklab
2022-11-25 6:07 dpdklab
2022-11-24 6:02 dpdklab
2022-11-23 6:08 dpdklab
2022-11-22 6:06 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=20221126061900.177EC60092@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).