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, Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw136315-136319 [PATCH] [5/5] net/mlx5: add support for fl
Date: Fri, 02 Feb 2024 05:49:27 -0800 (PST)	[thread overview]
Message-ID: <65bcf2e7.170a0220.2daff.3f5bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Friday, February 02 2024 11:56:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1d3700bd8452e2c62254499ef83f22f5ec7714dc

136315-136319 --> testing fail

Test environment and result as below:

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

==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
from ../lib/eal/include/rte_malloc.h:16,
from ../drivers/net/mlx5/mlx5.c:14:
../drivers/net/mlx5/mlx5_flow.h: In function 'mlx5_multi_pattern_segment_find':
../drivers/net/mlx5/mlx5_flow.h:1580:14: error: implicit declaration of function 'rte_flow_table_resizable'; did you mean 'rte_flow_validate'? [-Werror=implicit-function-declaration]
if (likely(!rte_flow_table_resizable(0, &table->cfg.attr)))
^
../lib/eal/include/rte_branch_prediction.h:30:39: note: in definition of macro 'likely'
#define likely(x) __builtin_expect(!!(x), 1)
^
../drivers/net/mlx5/mlx5_flow.h:1580:14: error: nested extern declaration of 'rte_flow_table_resizable' [-Werror=nested-externs]
if (likely(!rte_flow_table_resizable(0, &table->cfg.attr)))
^
../lib/eal/include/rte_branch_prediction.h:30:39: note: in definition of macro 'likely'
#define likely(x) __builtin_expect(!!(x), 1)
^
cc1: all warnings being treated as errors
[1673/2770] Linking static target drivers/librte_net_mlx4.a.
[1674/2770] Linking target drivers/librte_net_mlx4.so.24.1.
[1675/2770] Generating rte_net_ixgbe.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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

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

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.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)

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-02 13:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 13:49 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02 13:58 dpdklab
2024-02-02 13:56 dpdklab
2024-02-02 13:56 dpdklab
2024-02-02 13:56 dpdklab
2024-02-02 13:55 dpdklab
2024-02-02 13:54 dpdklab
2024-02-02 13:54 dpdklab
2024-02-02 13:53 dpdklab
2024-02-02 13:52 dpdklab
2024-02-02 13:51 dpdklab
2024-02-02 13:50 dpdklab
2024-02-02 13:50 dpdklab
2024-02-02 13:50 dpdklab
2024-02-02 13:49 dpdklab
2024-02-02 13:49 dpdklab
2024-02-02 13:49 dpdklab
2024-02-02 13:49 dpdklab
2024-02-02 13:49 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:48 dpdklab
2024-02-02 13:47 dpdklab
2024-02-02 13:47 dpdklab
2024-02-02 13:47 dpdklab
2024-02-02 13:47 dpdklab
2024-02-02 13:47 dpdklab
2024-02-02 13:46 dpdklab
2024-02-02 13:46 dpdklab
2024-02-02 13:46 dpdklab
2024-02-02 13:46 dpdklab
2024-02-02 13:45 dpdklab
2024-02-02 13:45 dpdklab
2024-02-02 13:45 dpdklab
2024-02-02 13:45 dpdklab
2024-02-02 13:44 dpdklab
2024-02-02 13:44 dpdklab
2024-02-02 13:44 dpdklab
2024-02-02 13:43 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=65bcf2e7.170a0220.2daff.3f5bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=getelson@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).