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, Zhichao Zeng <zhichaox.zeng@intel.com>
Subject: |FAILURE| pw135182 [PATCH] [v2] net/iavf: support rte flow with mask
Date: Thu, 14 Dec 2023 15:30:14 -0800 (PST)	[thread overview]
Message-ID: <657b9006.170a0220.60480.8179SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Thursday, December 14 2023 06:08:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135182 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Alpine (dpdk_meson_compile): ====
[1063/2667] Compiling C object 'drivers/a715181@@tmp_rte_net_iavf@sta/net_iavf_iavf_fdir.c.o'.
^[[01m^[[K../drivers/net/iavf/iavf_fdir.c:^[[m^[[K In function '^[[01m^[[Kiavf_fdir_parse_pattern^[[m^[[K':
^[[01m^[[K../drivers/net/iavf/iavf_fdir.c:1037:29:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Kthe comparison will always evaluate as '^[[01m^[[Ktrue^[[m^[[K' for the address of '^[[01m^[[Ksrc_addr^[[m^[[K' will never be NULL [^[[01;31m^[[K-Werror=address^[[m^[[K]
1037 |                         if (^[[01;31m^[[Kipv6_mask^[[m^[[K->hdr.src_addr)
|                             ^[[01;31m^[[K^~~~~~~~~^[[m^[[K
In file included from ^[[01m^[[K../lib/ethdev/rte_flow.h:25^[[m^[[K,
from ^[[01m^[[K../lib/ethdev/rte_eth_ctrl.h:11^[[m^[[K,
from ^[[01m^[[K../lib/ethdev/rte_ethdev.h:1452^[[m^[[K,
from ^[[01m^[[K../lib/ethdev/ethdev_driver.h:25^[[m^[[K,
from ^[[01m^[[K../drivers/net/iavf/iavf_fdir.c:14^[[m^[[K:
^[[01m^[[K../lib/net/rte_ip.h:528:18:^[[m^[[K ^[[01;36m^[[Knote: ^[[m^[[K'^[[01m^[[Ksrc_addr^[[m^[[K' declared here
528 |         uint8_t  ^[[01;36m^[[Ksrc_addr^[[m^[[K[16];  /**< IP address of source host. */
|                  ^[[01;36m^[[K^~~~~~~~^[[m^[[K
^[[01m^[[K../drivers/net/iavf/iavf_fdir.c:1039:29:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Kthe comparison will always evaluate as '^[[01m^[[Ktrue^[[m^[[K' for the address of '^[[01m^[[Kdst_addr^[[m^[[K' will never be NULL [^[[01;31m^[[K-Werror=address^[[m^[[K]
1039 |                         if (^[[01;31m^[[Kipv6_mask^[[m^[[K->hdr.dst_addr)
|                             ^[[01;31m^[[K^~~~~~~~~^[[m^[[K
^[[01m^[[K../lib/net/rte_ip.h:529:18:^[[m^[[K ^[[01;36m^[[Knote: ^[[m^[[K'^[[01m^[[Kdst_addr^[[m^[[K' declared here
529 |         uint8_t  ^[[01;36m^[[Kdst_addr^[[m^[[K[16];  /**< IP address of destination host(s). */
|                  ^[[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

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 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

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

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

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

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

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

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 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-14 23:30 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 23:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-15  0:10 dpdklab
2023-12-14 23:48 dpdklab
2023-12-14 23:35 dpdklab
2023-12-14 23:35 dpdklab
2023-12-14 23:35 dpdklab
2023-12-14 23:33 dpdklab
2023-12-14 23:33 dpdklab
2023-12-14 23:32 dpdklab
2023-12-14 23:32 dpdklab
2023-12-14 23:32 dpdklab
2023-12-14 23:32 dpdklab
2023-12-14 23:32 dpdklab
2023-12-14 23:31 dpdklab
2023-12-14 23:30 dpdklab
2023-12-14 23:30 dpdklab
2023-12-14 23:29 dpdklab
2023-12-14 23:29 dpdklab
2023-12-14 23:29 dpdklab
2023-12-14 23:29 dpdklab
2023-12-14 23:29 dpdklab
2023-12-14 23:29 dpdklab
2023-12-14 23:28 dpdklab
2023-12-14 23:28 dpdklab
2023-12-14 23:28 dpdklab
2023-12-14 23:27 dpdklab
2023-12-14 23:24 dpdklab
2023-12-14 23:24 dpdklab
2023-12-14 23:23 dpdklab
2023-12-14 23:23 dpdklab
2023-12-14 23:23 dpdklab
2023-12-14 23:21 dpdklab
2023-12-14 23:14 dpdklab
2023-12-14 23:12 dpdklab
2023-12-14 23:11 dpdklab
2023-12-14 23:10 dpdklab
2023-12-14 22:57 dpdklab
2023-12-14 22:54 dpdklab
2023-12-14 22:53 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=657b9006.170a0220.60480.8179SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=zhichaox.zeng@intel.com \
    /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).