From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw94297 [PATCH] [v2] bus: clarify log for non-NUMA-aware devices
Date: Wed, 16 Jun 2021 07:36:11 -0400 (EDT) [thread overview]
Message-ID: <20210616113611.DD9C030681@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 8031 bytes --]
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/94297
_Testing issues_
Submitter: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Date: Wednesday, June 16 2021 10:07:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2ca92f54410400af76a1f0bc3bfecc8077e282aa
94297 --> testing fail
Test environment and result as below:
+---------------------+----------------------+-------------------+--------------------+----------------+
| Environment | dpdk_mingw64_compile | dpdk_compile_spdk | dpdk_meson_compile | dpdk_unit_test |
+=====================+======================+===================+====================+================+
| Windows Server 2019 | PASS | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu 18.04 | SKIPPED | PASS | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 31 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu 18.04 ARM | SKIPPED | SKIPPED | FAIL | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+----------------+
| FreeBSD 13 | SKIPPED | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+----------------+
| FreeBSD 11.2 | SKIPPED | SKIPPED | PASS | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+----------------+
| openSUSE Leap 15 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 32 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| CentOS 8 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| RHEL 7 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| CentOS Stream 8 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Arch Linux | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu20.04 | SKIPPED | SKIPPED | FAIL | SKIPPED |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 34 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu 20.04 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| RHEL8 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 34 clang | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 33 | SKIPPED | SKIPPED | PASS | PASS |
+---------------------+----------------------+-------------------+--------------------+----------------+
==== 20 line log output for Ubuntu 18.04 ARM (dpdk_meson_compile): ====
[642/2904] Generating table.sym_chk with a custom command (wrapped by meson to capture output)
[643/2904] Generating regexdev.sym_chk with a custom command (wrapped by meson to capture output)
[644/2904] Generating fib.sym_chk with a custom command (wrapped by meson to capture output)
[645/2904] Generating cmdline.sym_chk with a custom command (wrapped by meson to capture output)
[646/2904] Generating rte_common_iavf.sym_chk with a custom command (wrapped by meson to capture output)
[647/2904] Generating bbdev.sym_chk with a custom command (wrapped by meson to capture output)
[648/2904] Generating compressdev.sym_chk with a custom command (wrapped by meson to capture output)
[649/2904] Generating rte_common_octeontx.sym_chk with a custom command (wrapped by meson to capture output)
[650/2904] Generating port.sym_chk with a custom command (wrapped by meson to capture output)
[651/2904] Generating rib.sym_chk with a custom command (wrapped by meson to capture output)
[652/2904] Generating vhost.sym_chk with a custom command (wrapped by meson to capture output)
[653/2904] Generating rte_common_dpaax.sym_chk with a custom command (wrapped by meson to capture output)
[654/2904] Generating graph.sym_chk with a custom command (wrapped by meson to capture output)
[655/2904] Generating cryptodev.sym_chk with a custom command (wrapped by meson to capture output)
[656/2904] Generating eventdev.sym_chk with a custom command (wrapped by meson to capture output)
[657/2904] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[658/2904] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[659/2904] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
[1] Error running command.
==== 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
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
FreeBSD 13
Kernel: 13.0
Compiler: gcc 10.2.0
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
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
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)
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
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Ubuntu20.04
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/17407/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-06-16 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 11:36 dpdklab [this message]
2021-06-19 17:01 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=20210616113611.DD9C030681@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).