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, Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: |FAILURE| pw141110-141117 [PATCH] [v2,8/8] net/mlx5: add async flow
Date: Wed, 12 Jun 2024 22:22:48 -0700 (PDT)	[thread overview]
Message-ID: <666a8228.170a0220.5d53c.1379SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240612162426.978117-9-dsosnowski@nvidia.com>

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

_Testing issues_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, June 12 2024 16:24:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e

141110-141117 --> testing issues

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Debian 12           | FAIL           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+
| Fedora 39           | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| RHEL9               | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_unit_test): ====
[1750/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_txq.c.o'.
[1751/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_txpp.c.o'.
[1752/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_vlan.c.o'.
[1753/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_utils.c.o'.
[1754/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_devx.c.o'.
[1755/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_nta_rss.c.o'.
[1756/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_geneve.c.o'.
[1757/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_hw.c.o'.
FAILED: drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_hw.c.o
ccache cc -Idrivers/a715181@@tmp_rte_net_mlx5@sta -Idrivers -I../drivers -Idrivers/net/mlx5 -I../drivers/net/mlx5 -Idrivers/net/mlx5/linux -I../drivers/net/mlx5/linux -Idrivers/net/mlx5/hws -I../drivers/net/mlx5/hws -Ilib/ethdev -I../lib/ethdev -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Idrivers/common/mlx5 -I../drivers/common/mlx5 -Idrivers/common/mlx5/lin
 ux -I../drivers/common/mlx5/linux -Idrivers/bus/auxiliary -I../drivers/bus/auxiliary -I/usr/include/libnl3 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -std=c11 -Wno-strict-prototypes -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -UPEDANTIC -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.mlx5 -MD -MQ 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_hw.c.o' -MF 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_flow_hw.c.o.d' -o 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_f
 low_hw.c.o' -c ../drivers/net/mlx5/mlx5_flow_hw.c
../drivers/net/mlx5/mlx5_flow_hw.c: In function 'flow_hw_is_item_masked':
../drivers/net/mlx5/mlx5_flow_hw.c:16208:24: error: 'RTE_FLOW_CONV_OP_ITEM_MASK' undeclared (first use in this function); did you mean 'RTE_FLOW_CONV_OP_ITEM_NAME'?
16208 |   size = rte_flow_conv(RTE_FLOW_CONV_OP_ITEM_MASK, NULL, 0, item, NULL);
|                        ^~~~~~~~~~~~~~~~~~~~~~~~~~
|                        RTE_FLOW_CONV_OP_ITEM_NAME
../drivers/net/mlx5/mlx5_flow_hw.c:16208:24: note: each undeclared identifier is reported only once for each function it appears in
[1758/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_nompw.c.o'.
[1759/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_empw.c.o'.
[1760/2869] Compiling C object 'drivers/a715181@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_tx_txpp.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-13  5:47 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240612162426.978117-9-dsosnowski@nvidia.com>
2024-06-12 16:00 ` |SUCCESS| pw141110-141117 [PATCH v2 8/8] net/mlx5: add async flow operation validation qemudev
2024-06-12 16:05 ` qemudev
2024-06-12 16:26 ` |SUCCESS| pw141117 " checkpatch
2024-06-13  2:00 ` |WARNING| pw141110-141117 [PATCH] [v2,8/8] net/mlx5: add async flow dpdklab
2024-06-13  2:12 ` dpdklab
2024-06-13  2:41 ` dpdklab
2024-06-13  2:42 ` dpdklab
2024-06-13  3:26 ` dpdklab
2024-06-13  3:32 ` dpdklab
2024-06-13  3:38 ` dpdklab
2024-06-13  3:43 ` dpdklab
2024-06-13  3:56 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:50 ` |FAILURE| " dpdklab
2024-06-13  4:50 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:51 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:52 ` dpdklab
2024-06-13  4:53 ` dpdklab
2024-06-13  4:53 ` dpdklab
2024-06-13  4:53 ` dpdklab
2024-06-13  4:53 ` dpdklab
2024-06-13  4:53 ` dpdklab
2024-06-13  4:54 ` dpdklab
2024-06-13  4:54 ` dpdklab
2024-06-13  4:54 ` dpdklab
2024-06-13  4:54 ` dpdklab
2024-06-13  4:55 ` |WARNING| " dpdklab
2024-06-13  4:55 ` |FAILURE| " dpdklab
2024-06-13  4:55 ` dpdklab
2024-06-13  4:56 ` dpdklab
2024-06-13  4:56 ` dpdklab
2024-06-13  4:56 ` dpdklab
2024-06-13  4:57 ` dpdklab
2024-06-13  4:57 ` dpdklab
2024-06-13  4:57 ` |WARNING| " dpdklab
2024-06-13  4:58 ` |FAILURE| " dpdklab
2024-06-13  4:58 ` dpdklab
2024-06-13  4:58 ` dpdklab
2024-06-13  4:59 ` dpdklab
2024-06-13  4:59 ` dpdklab
2024-06-13  5:00 ` dpdklab
2024-06-13  5:00 ` dpdklab
2024-06-13  5:00 ` dpdklab
2024-06-13  5:01 ` dpdklab
2024-06-13  5:01 ` dpdklab
2024-06-13  5:02 ` dpdklab
2024-06-13  5:02 ` dpdklab
2024-06-13  5:02 ` dpdklab
2024-06-13  5:02 ` dpdklab
2024-06-13  5:03 ` dpdklab
2024-06-13  5:03 ` dpdklab
2024-06-13  5:04 ` dpdklab
2024-06-13  5:04 ` dpdklab
2024-06-13  5:04 ` dpdklab
2024-06-13  5:05 ` dpdklab
2024-06-13  5:06 ` dpdklab
2024-06-13  5:07 ` dpdklab
2024-06-13  5:07 ` dpdklab
2024-06-13  5:10 ` dpdklab
2024-06-13  5:10 ` |WARNING| " dpdklab
2024-06-13  5:10 ` |FAILURE| " dpdklab
2024-06-13  5:22 ` dpdklab
2024-06-13  5:22 ` dpdklab [this message]
2024-06-13  5:23 ` dpdklab
2024-06-13  5:23 ` dpdklab
2024-06-13  5:24 ` dpdklab
2024-06-13  5:25 ` dpdklab
2024-06-13  5:31 ` 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=666a8228.170a0220.5d53c.1379SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=dsosnowski@nvidia.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).