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, Akhil Goyal <gakhil@marvell.com>
Subject: |FAILURE| pw128535-128549 [PATCH] [v3,15/15] net/cnxk: add MACsec st
Date: Tue, 13 Jun 2023 02:48:16 -0700 (PDT)	[thread overview]
Message-ID: <64883b60.810a0220.29708.d830SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Tuesday, June 13 2023 07:16:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:050de60d8a5cef8b7c10b4471905ca8bf69d670e

128535-128549 --> testing fail

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+
| CentOS Stream 9 (ARM)    | PASS           |
+--------------------------+----------------+
| Ubuntu 20.04 (ARM)       | PASS           |
+--------------------------+----------------+
| CentOS Stream 9          | PASS           |
+--------------------------+----------------+
| Fedora 37 (ARM)          | PASS           |
+--------------------------+----------------+
| Fedora 38 (ARM)          | PASS           |
+--------------------------+----------------+
| CentOS Stream 8          | PASS           |
+--------------------------+----------------+
| Fedora 37                | PASS           |
+--------------------------+----------------+
| Ubuntu 22.04             | PASS           |
+--------------------------+----------------+
| Ubuntu 20.04             | PASS           |
+--------------------------+----------------+
| RHEL 7                   | FAIL           |
+--------------------------+----------------+
| Fedora 38                | PASS           |
+--------------------------+----------------+
| Debian Buster            | PASS           |
+--------------------------+----------------+
| Debian Bullseye          | PASS           |
+--------------------------+----------------+
| RHEL8                    | PASS           |
+--------------------------+----------------+

==== 20 line log output for RHEL 7 (dpdk_unit_test): ====
../drivers/net/cnxk/cnxk_ethdev_mcs.c: In function 'mcs_resource_alloc':
../drivers/net/cnxk/cnxk_ethdev_mcs.c:14:9: error: missing braces around initializer [-Werror=missing-braces]
struct roc_mcs_alloc_rsrc_rsp rsp = {0};
^
../drivers/net/cnxk/cnxk_ethdev_mcs.c:14:9: error: (near initialization for 'rsp.flow_ids') [-Werror=missing-braces]
../drivers/net/cnxk/cnxk_ethdev_mcs.c: In function 'cnxk_eth_macsec_sa_create':
../drivers/net/cnxk/cnxk_ethdev_mcs.c:58:9: error: missing braces around initializer [-Werror=missing-braces]
struct roc_mcs_sa_plcy_write_req req = {0};
^
../drivers/net/cnxk/cnxk_ethdev_mcs.c:58:9: error: (near initialization for 'req.plcy') [-Werror=missing-braces]
../drivers/net/cnxk/cnxk_ethdev_mcs.c: In function 'cnxk_mcs_flow_configure':
../drivers/net/cnxk/cnxk_ethdev_mcs.c:399:9: error: missing braces around initializer [-Werror=missing-braces]
struct roc_mcs_flowid_entry_write_req req = {0};
^
../drivers/net/cnxk/cnxk_ethdev_mcs.c:399:9: error: (near initialization for 'req.data') [-Werror=missing-braces]
cc1: all warnings being treated as errors
[1167/3037] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command.
[1168/3037] Compiling C object 'drivers/a715181@@tmp_rte_net_cnxk@sta/net_cnxk_cnxk_ethdev_cman.c.o'.
[1169/3037] Generating rte_net_bond.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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)

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-13  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  9:48 dpdklab [this message]
2023-06-13 12:25 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=64883b60.810a0220.29708.d830SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.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).