automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw142503-142505 [PATCH] [v2,3/3] net/hns3: fix Rx packet w
Date: Thu, 18 Jul 2024 08:38:02 -0700 (PDT)	[thread overview]
Message-ID: <669936da.170a0220.7c7f2.3326SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240718114806.577298-4-haijie1@huawei.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/142505

_Testing issues_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Thursday, July 18 2024 11:48:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3317515e9377c13e458e31a64f8987a9d1f2eaf6

142503-142505 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#241440

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | WARN           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Fedora 38           | WARN           |
+---------------------+----------------+
| Fedora 37           | WARN           |
+---------------------+----------------+
| Debian 12           | PEND           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 39           | PEND           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Ubuntu 20.04        | PEND           |
+---------------------+----------------+
| openSUSE Leap 15    | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+
| RHEL9               | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | PEND           |
+---------------------+----------------+

==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
../drivers/net/hns3/hns3_rxtx.c:2454:18: note: object 'crc' of size 4
2454 |         uint32_t crc;
|                  ^~~
In function 'rte_mov15_or_less',
inlined from 'rte_memcpy_aligned' at ../lib/eal/x86/include/rte_memcpy.h:706:10,
inlined from 'rte_memcpy' at ../lib/eal/x86/include/rte_memcpy.h:755:10,
inlined from 'hns3_recalculate_crc' at ../drivers/net/hns3/hns3_rxtx.c:2471:2,
inlined from 'hns3_recv_pkts_simple' at ../drivers/net/hns3/hns3_rxtx.c:2571:4:
../lib/eal/x86/include/rte_memcpy.h:83: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]
83 |                         ((const struct rte_uint64_alias *)src)->val;
|                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
../drivers/net/hns3/hns3_rxtx.c: In function 'hns3_recv_pkts_simple':
../drivers/net/hns3/hns3_rxtx.c:2454:18: note: object 'crc' of size 4
2454 |         uint32_t crc;
|                  ^~~
cc1: all warnings being treated as errors
[1532/2899] Compiling C object 'drivers/a715181@@tmp_rte_net_hns3@sta/net_hns3_hns3_dump.c.o'.
[1533/2899] Compiling C object 'drivers/net/i40e/1b39a87@@i40e_avx2_lib@sta/i40e_rxtx_vec_avx2.c.o'.
[1534/2899] Compiling C object 'drivers/net/i40e/1b39a87@@i40e_avx512_lib@sta/i40e_rxtx_vec_avx512.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30553/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-07-18 15:38 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240718114806.577298-4-haijie1@huawei.com>
2024-07-18 11:23 ` |SUCCESS| pw142503-142505 [PATCH v2 3/3] net/hns3: fix Rx packet without CRC data qemudev
2024-07-18 11:28 ` qemudev
2024-07-18 11:49 ` |SUCCESS| pw142505 " checkpatch
2024-07-18 14:52 ` |PENDING| pw142503-142505 [PATCH] [v2,3/3] net/hns3: fix Rx packet w dpdklab
2024-07-18 14:56 ` |SUCCESS| " dpdklab
2024-07-18 14:58 ` |PENDING| " dpdklab
2024-07-18 15:02 ` dpdklab
2024-07-18 15:11 ` |SUCCESS| " dpdklab
2024-07-18 15:13 ` |PENDING| " dpdklab
2024-07-18 15:14 ` dpdklab
2024-07-18 15:15 ` |SUCCESS| " dpdklab
2024-07-18 15:16 ` dpdklab
2024-07-18 15:16 ` dpdklab
2024-07-18 15:16 ` |PENDING| " dpdklab
2024-07-18 15:16 ` |SUCCESS| " dpdklab
2024-07-18 15:17 ` |PENDING| " dpdklab
2024-07-18 15:18 ` dpdklab
2024-07-18 15:18 ` dpdklab
2024-07-18 15:19 ` dpdklab
2024-07-18 15:19 ` dpdklab
2024-07-18 15:20 ` |SUCCESS| " dpdklab
2024-07-18 15:20 ` |PENDING| " dpdklab
2024-07-18 15:22 ` dpdklab
2024-07-18 15:23 ` |FAILURE| " dpdklab
2024-07-18 15:23 ` |PENDING| " dpdklab
2024-07-18 15:23 ` |SUCCESS| " dpdklab
2024-07-18 15:24 ` |PENDING| " dpdklab
2024-07-18 15:24 ` |SUCCESS| " dpdklab
2024-07-18 15:27 ` dpdklab
2024-07-18 15:28 ` |PENDING| " dpdklab
2024-07-18 15:30 ` dpdklab
2024-07-18 15:31 ` |FAILURE| " dpdklab
2024-07-18 15:32 ` dpdklab
2024-07-18 15:32 ` |SUCCESS| " dpdklab
2024-07-18 15:35 ` |FAILURE| " dpdklab
2024-07-18 15:36 ` dpdklab
2024-07-18 15:36 ` dpdklab
2024-07-18 15:36 ` |PENDING| " dpdklab
2024-07-18 15:36 ` dpdklab
2024-07-18 15:37 ` dpdklab
2024-07-18 15:38 ` dpdklab [this message]
2024-07-18 15:38 ` |SUCCESS| " dpdklab
2024-07-18 15:39 ` |FAILURE| " dpdklab
2024-07-18 15:40 ` |PENDING| " dpdklab
2024-07-18 15:40 ` dpdklab
2024-07-18 15:43 ` dpdklab
2024-07-18 15:43 ` dpdklab
2024-07-18 15:43 ` |FAILURE| " dpdklab
2024-07-18 15:45 ` dpdklab
2024-07-18 15:45 ` |PENDING| " dpdklab
2024-07-18 15:48 ` dpdklab
2024-07-18 15:48 ` dpdklab
2024-07-18 15:50 ` |FAILURE| " dpdklab
2024-07-18 15:51 ` dpdklab
2024-07-18 15:51 ` |SUCCESS| " dpdklab
2024-07-18 15:52 ` |PENDING| " dpdklab
2024-07-18 15:52 ` |FAILURE| " dpdklab
2024-07-18 15:53 ` |PENDING| " dpdklab
2024-07-18 15:55 ` dpdklab
2024-07-18 15:56 ` |SUCCESS| " dpdklab
2024-07-18 15:56 ` |PENDING| " dpdklab
2024-07-18 15:58 ` |SUCCESS| " dpdklab
2024-07-18 15:59 ` |PENDING| " dpdklab
2024-07-18 16:00 ` dpdklab
2024-07-18 16:00 ` |FAILURE| " dpdklab
2024-07-18 16:02 ` |SUCCESS| " dpdklab
2024-07-18 16:03 ` dpdklab
2024-07-18 16:03 ` |FAILURE| " dpdklab
2024-07-18 16:03 ` |PENDING| " dpdklab
2024-07-18 16:04 ` |FAILURE| " dpdklab
2024-07-18 16:06 ` dpdklab
2024-07-18 16:10 ` |WARNING| " dpdklab
2024-07-18 16:19 ` |PENDING| " dpdklab
2024-07-18 16:20 ` dpdklab
2024-07-18 16:23 ` |FAILURE| " dpdklab
2024-07-18 16:25 ` |PENDING| " dpdklab
2024-07-18 16:27 ` dpdklab
2024-07-18 16:30 ` |FAILURE| " dpdklab
2024-07-18 16:30 ` dpdklab
2024-07-18 16:30 ` dpdklab
2024-07-18 16:33 ` |PENDING| " dpdklab
2024-07-18 16:33 ` |FAILURE| " dpdklab
2024-07-18 16:33 ` dpdklab
2024-07-18 16:34 ` dpdklab
2024-07-18 16:36 ` dpdklab
2024-07-18 16:42 ` dpdklab
2024-07-18 16:43 ` |PENDING| " dpdklab
2024-07-18 16:43 ` |FAILURE| " dpdklab
2024-07-18 16:44 ` |PENDING| " dpdklab
2024-07-18 16:45 ` |FAILURE| " dpdklab
2024-07-18 16:46 ` |PENDING| " dpdklab
2024-07-18 16:47 ` dpdklab
2024-07-18 16:49 ` |FAILURE| " dpdklab
2024-07-18 16:51 ` dpdklab
2024-07-18 16:53 ` dpdklab
2024-07-18 16:53 ` |PENDING| " dpdklab
2024-07-18 16:55 ` |FAILURE| " dpdklab
2024-07-18 16:55 ` |PENDING| " dpdklab
2024-07-18 16:56 ` dpdklab
2024-07-18 16:56 ` dpdklab
2024-07-18 16:58 ` dpdklab
2024-07-18 17:03 ` dpdklab
2024-07-18 17:03 ` dpdklab
2024-07-18 17:03 ` |FAILURE| " dpdklab
2024-07-18 17:06 ` |PENDING| " dpdklab
2024-07-18 17:07 ` dpdklab
2024-07-18 17:09 ` |SUCCESS| " dpdklab
2024-07-18 17:15 ` |PENDING| " dpdklab
2024-07-18 17:18 ` dpdklab
2024-07-18 17:21 ` dpdklab
2024-07-18 17:30 ` dpdklab
2024-07-18 17:39 ` dpdklab
2024-07-18 17:54 ` dpdklab
2024-07-18 17:57 ` |SUCCESS| " dpdklab
2024-07-18 22:19 ` 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=669936da.170a0220.7c7f2.3326SMTPIN_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).