From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chaoyong He <chaoyong.he@corigine.com>
Subject: |FAILURE| pw130704-130730 [PATCH] [27/27] net/nfp: extend the usage
Date: Fri, 25 Aug 2023 00:18:00 -0700 (PDT) [thread overview]
Message-ID: <64e855a8.170a0220.d3feb.1c38SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130730
_Testing issues_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, August 24 2023 11:09:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c
130704-130730 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Fedora 37 (dpdk_meson_compile): ====
888 | *interface = dsn & 0xffff;
| ~~~~~~~~~~~^~~~~~~~~~~~~~
../drivers/net/nfp/nfpcore/nfp6000_pcie.c:882:18: note: 'dsn' was declared here
882 | uint64_t dsn;
| ^~~
../drivers/net/nfp/nfpcore/nfp6000_pcie.c: In function 'nfp6000_get_serial':
../drivers/net/nfp/nfpcore/nfp6000_pcie.c:899:18: error: 'dsn' may be used uninitialized [-Werror=maybe-uninitialized]
899 | uint64_t dsn;
| ^~~
In function 'nfp6000_get_interface',
inlined from 'nfp_cpp_from_nfp6000_pcie' at ../drivers/net/nfp/nfpcore/nfp6000_pcie.c:1002:8:
../drivers/net/nfp/nfpcore/nfp6000_pcie.c:888:20: error: 'dsn' may be used uninitialized [-Werror=maybe-uninitialized]
888 | *interface = dsn & 0xffff;
| ~~~~~~~~~~~^~~~~~~~~~~~~~
../drivers/net/nfp/nfpcore/nfp6000_pcie.c: In function 'nfp_cpp_from_nfp6000_pcie':
../drivers/net/nfp/nfpcore/nfp6000_pcie.c:882:18: note: 'dsn' was declared here
882 | uint64_t dsn;
| ^~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27438/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-25 7:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 7:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-25 8:49 dpdklab
2023-08-25 8:11 dpdklab
2023-08-25 7:43 dpdklab
2023-08-25 7:42 dpdklab
2023-08-25 7:39 dpdklab
2023-08-25 7:38 dpdklab
2023-08-25 7:35 dpdklab
2023-08-25 7:35 dpdklab
2023-08-25 7:34 dpdklab
2023-08-25 7:34 dpdklab
2023-08-25 7:33 dpdklab
2023-08-25 7:31 dpdklab
2023-08-25 7:31 dpdklab
2023-08-25 7:31 dpdklab
2023-08-25 7:31 dpdklab
2023-08-25 7:31 dpdklab
2023-08-25 7:30 dpdklab
2023-08-25 7:30 dpdklab
2023-08-25 7:27 dpdklab
2023-08-25 7:25 dpdklab
2023-08-25 7:25 dpdklab
2023-08-25 7:25 dpdklab
2023-08-25 7:25 dpdklab
2023-08-25 7:24 dpdklab
2023-08-25 7:22 dpdklab
2023-08-25 7:21 dpdklab
2023-08-25 7:20 dpdklab
2023-08-25 7:16 dpdklab
2023-08-25 7:15 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=64e855a8.170a0220.d3feb.1c38SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chaoyong.he@corigine.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).