From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Anoob Joseph <anoobj@marvell.com>
Subject: |FAILURE| pw105166-105193 [PATCH] [v2, 29/29] crypto/cnxk: update microcode completion handling
Date: Fri, 17 Dec 2021 06:42:51 +0000 (UTC) [thread overview]
Message-ID: <20211217064251.B19D76025C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4325 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/105193
_Testing issues_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Thursday, December 16 2021 17:49:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:042f5a355a57b31a9f87824173a9d427b21abdb8
105166-105193 --> testing fail
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| RHEL 7 | FAIL |
+------------------+----------------+
| Fedora 32 | PASS |
+------------------+----------------+
| Fedora 34 clang | PASS |
+------------------+----------------+
| Fedora 33 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| CentOS 8 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Fedora 31 | PASS |
+------------------+----------------+
| Fedora 34 | PASS |
+------------------+----------------+
| Ubuntu 18.04 | PASS |
+------------------+----------------+
| Arch Linux | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
==== 20 line log output for RHEL 7 (dpdk_unit_test): ====
^
cc1: all warnings being treated as errors
[2209/3047] Linking static target drivers/librte_crypto_null.a
[2210/3047] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_rxtx.c.o
[2211/3047] Compiling C object drivers/libtmp_rte_crypto_virtio.a.p/crypto_virtio_virtio_pci.c.o
[2212/3047] Generating rte_crypto_octeontx.pmd.c with a custom command
[2213/3047] Generating eal.sym_chk with a meson_exe.py custom command
[2214/3047] Generating rte_crypto_openssl.pmd.c with a custom command
[2215/3047] Generating rte_crypto_bcmfs.sym_chk with a meson_exe.py custom command
[2216/3047] Generating rte_crypto_octeontx2.pmd.c with a custom command
[2217/3047] Generating rte_crypto_caam_jr.sym_chk with a meson_exe.py custom command
[2218/3047] Generating rte_crypto_scheduler.pmd.c with a custom command
[2219/3047] Generating rte_crypto_ccp.sym_chk with a meson_exe.py custom command
[2220/3047] Generating rte_crypto_mlx5.sym_chk with a meson_exe.py custom command
[2221/3047] Generating rte_crypto_dpaa_sec.sym_chk with a meson_exe.py custom command
[2222/3047] Generating rte_crypto_dpaa2_sec.sym_chk with a meson_exe.py custom command
[2223/3047] Generating rte_crypto_nitrox.sym_chk with a meson_exe.py custom command
[2224/3047] Generating rte_common_sfc_efx.sym_chk with a meson_exe.py custom command
[2225/3047] Generating rte_common_cnxk.sym_chk with a meson_exe.py custom command
ninja: build stopped: subcommand failed.
==== End log output ====
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 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
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)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.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)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20509/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-12-17 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 6:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 6:35 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=20211217064251.B19D76025C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=anoobj@marvell.com \
--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).