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, Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: [dpdk-test-report] |FAILURE| pw101196-101200 [PATCH] [v4, 5/5] net/mlx5: update modify field action
Date: Tue, 12 Oct 2021 15:59:28 -0400 (EDT)	[thread overview]
Message-ID: <20211012195928.428AA60524@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4679 bytes --]

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

_Testing issues_

Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, October 12 2021 10:49:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e0ae3db0c043cbdc4cc22bb60206f21ec4a82a02

101196-101200 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Arch Linux       | FAIL           |
+------------------+----------------+
| Ubuntu 18.04     | PASS           |
+------------------+----------------+
| CentOS 8         | FAIL           |
+------------------+----------------+
| Fedora 31        | PASS           |
+------------------+----------------+
| CentOS Stream 8  | FAIL           |
+------------------+----------------+
| Fedora 32        | FAIL           |
+------------------+----------------+
| openSUSE Leap 15 | FAIL           |
+------------------+----------------+
| RHEL 7           | FAIL           |
+------------------+----------------+
| RHEL8            | FAIL           |
+------------------+----------------+
| Ubuntu 20.04     | FAIL           |
+------------------+----------------+
| Fedora 34        | FAIL           |
+------------------+----------------+
| Fedora 33        | FAIL           |
+------------------+----------------+
| Fedora 34 clang  | PASS           |
+------------------+----------------+

==== 20 line log output for Fedora 33 (dpdk_unit_test): ====
|           ^~~~~~~~~
cc1: all warnings being treated as errors
[1818/2925] Generating rte_net_octeontx.sym_chk with a custom command (wrapped by meson to capture output)
[1819/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_flow_ctrl.c.o
[1820/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_flow_dump.c.o
[1821/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_ethdev_irq.c.o
[1822/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_flow_utils.c.o
[1823/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_flow_parse.c.o
[1824/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_ethdev_devargs.c.o
[1825/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_ethdev_ops.c.o
[1826/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_ethdev_sec.c.o
[1827/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_ethdev_debug.c.o
[1828/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_ethdev.c.o
[1829/2925] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1830/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_tx.c.o
[1831/2925] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.o
[1832/2925] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.o
[1833/2925] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.o
[1834/2925] Compiling C object drivers/libtmp_rte_net_octeontx2.a.p/net_octeontx2_otx2_rx.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

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

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

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

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

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)

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

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-12 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 19:59 dpdklab [this message]
2021-10-13  1:55 dpdklab
2021-10-14 14:44 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=20211012195928.428AA60524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=viacheslavo@nvidia.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).