From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| [GIT MASTER] 4113ddd45293d7b26ff4033bfd86cef03d29124f
Date: Fri, 16 Apr 2021 10:35:02 -0400 (EDT) [thread overview]
Message-ID: <20210416143503.011D419D9F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 5634 bytes --]
_Testing issues_
Branch: dpdk-next-eventdev
4113ddd45293d7b26ff4033bfd86cef03d29124f --> testing fail
Test environment and result as below:
+---------------------+----------------------+--------------------+----------------+-------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_unit_test | dpdk_compile_spdk |
+=====================+======================+====================+================+===================+
| Windows Server 2019 | PASS | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Ubuntu 18.04 | SKIPPED | PASS | PASS | PASS |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Ubuntu 18.04 ARM | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Fedora 31 | SKIPPED | PASS | SKIPPED | PASS |
+---------------------+----------------------+--------------------+----------------+-------------------+
| openSUSE Leap 15 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Fedora 32 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| FreeBSD 11.2 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| RHEL 7 | SKIPPED | FAIL | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| CentOS Stream 8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| RHEL8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Arch Linux | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Ubuntu 20.04 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+----------------+-------------------+
==== 20 line log output for RHEL 7 (dpdk_meson_compile): ====
^
cc1: all warnings being treated as errors
[246/2686] Linking static target lib/librte_gso.a
[247/2686] Generating mbuf.sym_chk with a meson_exe.py custom command
[248/2686] Compiling C object lib/librte_ip_frag.a.p/librte_ip_frag_rte_ipv4_fragmentation.c.o
[249/2686] Compiling C object lib/librte_ip_frag.a.p/librte_ip_frag_rte_ipv6_fragmentation.c.o
[250/2686] Compiling C object lib/librte_ip_frag.a.p/librte_ip_frag_rte_ipv6_reassembly.c.o
[251/2686] Compiling C object lib/librte_ip_frag.a.p/librte_ip_frag_rte_ipv4_reassembly.c.o
[252/2686] Compiling C object lib/librte_table.a.p/librte_table_rte_table_acl.c.o
[253/2686] Generating metrics.sym_chk with a meson_exe.py custom command
[254/2686] Generating symbol file lib/librte_telemetry.so.21.2.p/librte_telemetry.so.21.2.symbols
[255/2686] Generating distributor.sym_chk with a meson_exe.py custom command
[256/2686] Generating efd.sym_chk with a meson_exe.py custom command
[257/2686] Generating gro.sym_chk with a meson_exe.py custom command
[258/2686] Generating bbdev.sym_chk with a meson_exe.py custom command
[259/2686] Generating compressdev.sym_chk with a meson_exe.py custom command
[260/2686] Generating cryptodev.sym_chk with a meson_exe.py custom command
[261/2686] Generating ethdev.sym_chk with a meson_exe.py custom command
[262/2686] Generating eal.sym_chk with a meson_exe.py custom command
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0 and gcc 8.1.0 (MinGW)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
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
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
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: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/14626/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-04-16 14:35 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=20210416143503.011D419D9F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@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).