automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Rongwei Liu <rongweil@nvidia.com>
Subject: |FAILURE| pw126174-126181 [PATCH] [v1, 8/8] net/mlx5: implement IPv6 routing push pop
Date: Mon, 17 Apr 2023 16:14:42 +0000 (UTC)	[thread overview]
Message-ID: <20230417161442.E2E6560092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/126181

_Testing issues_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Monday, April 17 2023 09:25:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd

126174-126181 --> testing fail

Test environment and result as below:

+------------------+--------------------+
|   Environment    | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13       | PASS               |
+------------------+--------------------+
| CentOS Stream 9  | FAIL               |
+------------------+--------------------+
| CentOS Stream 8  | PASS               |
+------------------+--------------------+
| Debian Bullseye  | FAIL               |
+------------------+--------------------+
| Ubuntu 22.04     | FAIL               |
+------------------+--------------------+
| RHEL8            | PASS               |
+------------------+--------------------+
| Ubuntu 20.04     | PASS               |
+------------------+--------------------+
| Debian Buster    | PASS               |
+------------------+--------------------+
| openSUSE Leap 15 | PASS               |
+------------------+--------------------+
| RHEL 7           | PASS               |
+------------------+--------------------+
| Alpine           | PASS               |
+------------------+--------------------+

==== 20 line log output for Ubuntu 22.04 (dpdk_meson_compile): ====
../drivers/net/mlx5/mlx5_flow_hw.c:1596:17: error: implicit conversion from enumeration type 'enum mlx5dr_action_reformat_type' to different enumeration type 'enum mlx5dr_action_type' [-Werror,-Wenum-conversion]
refmt_type = MLX5DR_ACTION_REFORMAT_TYPE_TNL_L2_TO_L2;
~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow_hw.c:1612:5: error: implicit conversion from enumeration type 'enum mlx5dr_action_reformat_type' to different enumeration type 'enum mlx5dr_action_type' [-Werror,-Wenum-conversion]
MLX5DR_ACTION_REFORMAT_TYPE_TNL_L3_TO_L2 :
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow_hw.c:1613:5: error: implicit conversion from enumeration type 'enum mlx5dr_action_reformat_type' to different enumeration type 'enum mlx5dr_action_type' [-Werror,-Wenum-conversion]
MLX5DR_ACTION_REFORMAT_TYPE_L2_TO_TNL_L3;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow_hw.c:1617:5: error: implicit conversion from enumeration type 'enum mlx5dr_action_reformat_type' to different enumeration type 'enum mlx5dr_action_type' [-Werror,-Wenum-conversion]
MLX5DR_ACTION_REFORMAT_TYPE_L2_TO_TNL_L2;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow_hw.c:1623:17: error: implicit conversion from enumeration type 'enum mlx5dr_action_reformat_type' to different enumeration type 'enum mlx5dr_action_type' [-Werror,-Wenum-conversion]
refmt_type = MLX5DR_ACTION_REFORMAT_TYPE_TNL_L2_TO_L2;
~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/mlx5/mlx5_flow_hw.c:1840:20: error: implicit conversion from enumeration type 'enum mlx5dr_action_type' to different enumeration type 'enum mlx5dr_action_reformat_type' [-Werror,-Wenum-conversion]
(priv->dr_ctx, refmt_type,
^~~~~~~~~~
8 errors generated.
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

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: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

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

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-17 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 16:14 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-17 18:47 dpdklab
2023-04-17 17:52 dpdklab
2023-04-17 16:36 dpdklab
2023-04-17 15:19 dpdklab
2023-04-17 14: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=20230417161442.E2E6560092@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=rongweil@nvidia.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).