From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jie Hai <haijie1@huawei.com>
Subject: |FAILURE| pw136411 [PATCH] net/hns3: fix Rx packet truncation when K
Date: Mon, 05 Feb 2024 18:05:36 -0800 (PST) [thread overview]
Message-ID: <65c193f0.050a0220.4db0e.29a8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/136411
_Testing issues_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Tuesday, February 06 2024 01:10:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f8ecc0053ca52cb2310a9e1834ea583167a793cd
136411 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Ubuntu 22.04 (dpdk_meson_compile): ====
73 | ((const struct rte_uint64_alias *)src)->val;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
../drivers/net/hns3/hns3_rxtx.c:2435:18: note: while referencing 'crc'
2435 | uint32_t crc;
| ^~~
In file included from ../lib/mempool/rte_mempool.h:49,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/net/rte_ether.h:22,
from ../lib/ethdev/rte_eth_ctrl.h:10,
from ../lib/ethdev/rte_ethdev.h:1453,
from ../lib/ethdev/ethdev_driver.h:25,
from ../drivers/net/hns3/hns3_rxtx.c:10:
../lib/eal/x86/include/rte_memcpy.h:73:63: error: array subscript 'const struct rte_uint64_alias[0]' is partly outside array bounds of 'uint32_t[1]' {aka 'unsigned int[1]'} [-Werror=array-bounds]
73 | ((const struct rte_uint64_alias *)src)->val;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
../drivers/net/hns3/hns3_rxtx.c:2435:18: note: while referencing 'crc'
2435 | uint32_t crc;
| ^~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
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
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29051/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-06 2:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 2:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 2:41 dpdklab
2024-02-06 2:37 dpdklab
2024-02-06 2:34 dpdklab
2024-02-06 2:34 dpdklab
2024-02-06 2:33 dpdklab
2024-02-06 2:32 dpdklab
2024-02-06 2:32 dpdklab
2024-02-06 2:31 dpdklab
2024-02-06 2:28 dpdklab
2024-02-06 2:28 dpdklab
2024-02-06 2:28 dpdklab
2024-02-06 2:10 dpdklab
2024-02-06 2:04 dpdklab
2024-02-06 2:04 dpdklab
2024-02-06 2:04 dpdklab
2024-02-06 2:03 dpdklab
2024-02-06 2:03 dpdklab
2024-02-06 2:03 dpdklab
2024-02-06 2:03 dpdklab
2024-02-06 2:03 dpdklab
2024-02-06 2:02 dpdklab
2024-02-06 2:02 dpdklab
2024-02-06 2:02 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=65c193f0.050a0220.4db0e.29a8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=haijie1@huawei.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).