From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: [dpdk-test-report] |FAILURE| pw100344-100357 [PATCH] [v2, 14/14] net/mlx5: handle flex item in flows
Date: Tue, 5 Oct 2021 02:52:38 -0400 (EDT) [thread overview]
Message-ID: <20211005065238.C2B936D535@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4434 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/100357
_Testing issues_
Submitter: Slava Ovsiienko <viacheslavo@nvidia.com>
Date: Friday, October 01 2021 19:34:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:086d426406bd3f6fac96a15bbd871c7fe714bc2d
100344-100357 --> testing fail
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Arch Linux | FAIL |
+------------------+----------------+
| CentOS 8 | FAIL |
+------------------+----------------+
| Fedora 31 | FAIL |
+------------------+----------------+
| Fedora 32 | FAIL |
+------------------+----------------+
| Ubuntu 18.04 | FAIL |
+------------------+----------------+
| RHEL 7 | FAIL |
+------------------+----------------+
| RHEL8 | FAIL |
+------------------+----------------+
| Ubuntu 20.04 | FAIL |
+------------------+----------------+
| Fedora 34 | FAIL |
+------------------+----------------+
| Fedora 33 | FAIL |
+------------------+----------------+
| Fedora 34 clang | FAIL |
+------------------+----------------+
| openSUSE Leap 15 | FAIL |
+------------------+----------------+
| CentOS Stream 8 | FAIL |
+------------------+----------------+
==== 20 line log output for CentOS Stream 8 (dpdk_unit_test): ====
^~~~
cc1: all warnings being treated as errors
[1691/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_meter.c.o
[1692/2918] Generating rte_net_i40e.sym_chk with a meson_exe.py custom command
[1693/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxtx.c.o
[1694/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_stats.c.o
[1695/2918] Generating rte_net_mlx4.sym_chk with a meson_exe.py custom command
[1696/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rxq.c.o
[1697/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_trigger.c.o
[1698/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx.c.o
[1699/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_txq.c.o
[1700/2918] Generating rte_net_ixgbe.sym_chk with a meson_exe.py custom command
[1701/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_rx.c.o
[1702/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow.c.o
[1703/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_mpw.c.o
[1704/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_nompw.c.o
[1705/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_flow_dv.c.o
[1706/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_empw.c.o
[1707/2918] Compiling C object drivers/libtmp_rte_net_mlx5.a.p/net_mlx5_mlx5_tx_txpp.c.o
ninja: build stopped: subcommand failed.
==== End log output ====
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
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
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.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)
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19121/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-05 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 6:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-05 3:06 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=20211005065238.C2B936D535@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).