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, Mingjin Ye <mingjinx.ye@intel.com>
Subject: |FAILURE| pw135424 [PATCH] net/iavf: add diagnostic support in TX pa
Date: Thu, 21 Dec 2023 06:13:15 -0800 (PST)	[thread overview]
Message-ID: <658447fb.0c0a0220.a8743.2e9dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/135424

_Testing issues_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thursday, December 21 2023 10:12:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135424 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | FAIL               | FAIL                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Alpine (dpdk_meson_compile): ====
[1055/2667] Linking static target drivers/librte_net_ice.a.
[1056/2667] Generating rte_net_ice.sym_chk with a meson_exe.py custom command.
[1057/2667] Linking static target drivers/net/ice/base/libice_base.a.
[1058/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_rxtx_vec_sse.c.o'.
[1059/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_fsub.c.o'.
[1060/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_ipsec_crypto.c.o'.
[1061/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_tm.c.o'.
[1062/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_hash.c.o'.
[1063/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_fdir.c.o'.
[1064/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_generic_flow.c.o'.
[1065/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_vchnl.c.o'.
[1066/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_rxtx.c.o'.
^[[01m^[[K../drivers/net/iavf/iavf_rxtx.c:^[[m^[[K In function '^[[01m^[[Kiavf_xmit_pkts_chain^[[m^[[K':
^[[01m^[[K../drivers/net/iavf/iavf_rxtx.c:3931:16:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[K'^[[01m^[[Kret^[[m^[[K' may be used uninitialized [^[[01;31m^[[K-Werror=maybe-uninitialized^[[m^[[K]
3931 |         return ^[[01;31m^[[Kret^[[m^[[K;
|                ^[[01;31m^[[K^~~^[[m^[[K
^[[01m^[[K../drivers/net/iavf/iavf_rxtx.c:3922:18:^[[m^[[K ^[[01;36m^[[Knote: ^[[m^[[K'^[[01m^[[Kret^[[m^[[K' was declared here
3922 |         uint16_t ^[[01;36m^[[Kret^[[m^[[K;
|                  ^[[01;36m^[[K^~~^[[m^[[K
cc1: all warnings being treated as errors
==== End log output ====

Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-21 14:13 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 14:13 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-21 16:00 dpdklab
2023-12-21 14:30 dpdklab
2023-12-21 14:19 dpdklab
2023-12-21 14:13 dpdklab
2023-12-21 14:12 dpdklab
2023-12-21 13:59 dpdklab
2023-12-21 13:57 dpdklab
2023-12-21 13:56 dpdklab
2023-12-21 13:56 dpdklab
2023-12-21 13:55 dpdklab
2023-12-21 13:54 dpdklab
2023-12-21 13:53 dpdklab
2023-12-21 13:52 dpdklab
2023-12-21 13:50 dpdklab
2023-12-21 13:48 dpdklab
2023-12-21 13:48 dpdklab
2023-12-21 13:45 dpdklab
2023-12-21 13:42 dpdklab
2023-12-21 13:32 dpdklab
2023-12-21 13:28 dpdklab
2023-12-21 13:28 dpdklab
2023-12-21 13:26 dpdklab
2023-12-21 13:26 dpdklab
2023-12-21 13:24 dpdklab
2023-12-21 13:23 dpdklab
2023-12-21 13:21 dpdklab
2023-12-21 13:16 dpdklab
2023-12-21 13:15 dpdklab
2023-12-21 13:13 dpdklab
2023-12-21 13:12 dpdklab
2023-12-21 13:12 dpdklab
2023-12-21 13:11 dpdklab
2023-12-21 13:03 dpdklab
2023-12-21 12:43 dpdklab
2023-12-21 12:40 dpdklab
2023-12-21 12:38 dpdklab
2023-12-21 12:28 dpdklab
2023-12-21 12:27 dpdklab
2023-12-21 12:25 dpdklab
2023-12-21 12:12 dpdklab
2023-12-21 12:11 dpdklab
2023-12-21 12:11 dpdklab
2023-12-21 12:10 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=658447fb.0c0a0220.a8743.2e9dSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mingjinx.ye@intel.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).