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
Subject: [dpdk-test-report] |FAILURE| [GIT MASTER] a46873e69d5ab1b544eee2f441e4d2bfe5995e4e
Date: Sat, 16 Oct 2021 14:45:02 -0400 (EDT)	[thread overview]
Message-ID: <20211016184502.D3B0760524@noxus.dpdklab.iol.unh.edu> (raw)

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

_Testing issues_

Branch: dpdk-next-net

a46873e69d5ab1b544eee2f441e4d2bfe5995e4e --> testing fail

Test environment and result as below:

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

==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
^~~
cc1: all warnings being treated as errors
[1296/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_fdir.c.o
[1297/2926] Generating rte_net_failsafe.sym_chk with a custom command (wrapped by meson to capture output)
[1298/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_flow.c.o
[1299/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_ethdev_vf.c.o
[1300/2926] Generating rte_net_fm10k.sym_chk with a custom command (wrapped by meson to capture output)
[1301/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_stats.c.o
[1302/2926] Generating rte_net_hinic.sym_chk with a custom command (wrapped by meson to capture output)
[1303/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_mp.c.o
[1304/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_ptp.c.o
[1305/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_tm.c.o
[1306/2926] Generating rte_bus_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[1307/2926] Generating rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[1308/2926] Compiling C object drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_rxtx.c.o
[1309/2926] Generating rte_common_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[1310/2926] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
[1311/2926] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[1312/2926] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

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)

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

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

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 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

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

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

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)

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

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/tarballs/17237/

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2021-10-16 18:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211016184502.D3B0760524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --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).