From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| [GIT MASTER] dde650220800850b58c81075cee3cf23c6fe593c
Date: Thu, 27 Jun 2024 04:45:47 -0700 (PDT) [thread overview]
Message-ID: <667d50eb.170a0220.ca3fe.2c55SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: dpdk-next-net-intel
dde650220800850b58c81075cee3cf23c6fe593c --> testing issues
Test environment and result as below:
+---------------------+--------------------+-------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PASS | PASS | FAIL |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2019 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------------+
==== 20 line log output for Windows Server 2022 (dpdk_mingw64_compile): ====
../drivers/net/ice/base/ice_ptp_hw.c:3287:7: error: 'val' may be used uninitialized in this function [-Werror=maybe-uninitialized]
val |= Q_REG_TX_MEM_GBL_CFG_LANE_TYPE_M;
^~
../drivers/net/ice/base/ice_ptp_hw.c: In function 'ice_read_phy_tstamp':
../drivers/net/ice/base/ice_ptp_hw.c:2716:6: error: 'lo' may be used uninitialized in this function [-Werror=maybe-uninitialized]
u32 lo, hi;
^~
../drivers/net/ice/base/ice_ptp_hw.c:2739:13: error: 'hi' may be used uninitialized in this function [-Werror=maybe-uninitialized]
*tstamp = ((u64)hi) << TS_PHY_HIGH_S | ((u64)lo & TS_PHY_LOW_M);
~^~~~~~~~
../drivers/net/ice/base/ice_ptp_hw.c:2716:10: note: 'hi' was declared here
u32 lo, hi;
^~
cc1.exe: all warnings being treated as errors
[270/748] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_xlt_kb.c.obj
[271/748] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_bst_tcam.c.obj
[272/748] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_fdir.c.obj
[273/748] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_flg_rd.c.obj
[274/748] Compiling C object drivers/net/ice/libice_avx2_lib.a.p/ice_rxtx_vec_avx2.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29614/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-06-27 11:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 11:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 13:09 dpdklab
2024-06-27 12:49 dpdklab
2024-06-27 12:46 dpdklab
2024-06-27 12:44 dpdklab
2024-06-27 12:44 dpdklab
2024-06-27 12:42 dpdklab
2024-06-27 12:38 dpdklab
2024-06-27 12:38 dpdklab
2024-06-27 12:32 dpdklab
2024-06-27 12:31 dpdklab
2024-06-27 12:28 dpdklab
2024-06-27 12:28 dpdklab
2024-06-27 12:26 dpdklab
2024-06-27 12:25 dpdklab
2024-06-27 12:25 dpdklab
2024-06-27 12:24 dpdklab
2024-06-27 11:48 dpdklab
2024-06-27 11:40 dpdklab
2024-06-27 11:38 dpdklab
2024-06-27 11:37 dpdklab
2024-06-27 11:34 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=667d50eb.170a0220.ca3fe.2c55SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).