From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw92776 [PATCH] test/crypto: copy offset data to oop dst buffer
Date: Tue, 4 May 2021 20:15:05 -0400 (EDT) [thread overview]
Message-ID: <20210505001505.E84A48904A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3424 bytes --]
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/92776
_Testing issues_
Submitter: Kai Ji <kai.ji@intel.com>
Date: Tuesday, May 04 2021 23:26:53
DPDK git baseline: Repo:dpdk-next-crypto
Branch: master
CommitID:8b6b2bf6b5788c56765e128e5af3ab73b8eae69d
92776 --> testing fail
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 18.04 ARM | FAIL |
+------------------+----------+
| RHEL 7 | FAIL |
+------------------+----------+
| Ubuntu 18.04 | FAIL |
+------------------+----------+
| RHEL8 | FAIL |
+------------------+----------+
| CentOS 8 | FAIL |
+------------------+----------+
| Ubuntu 20.04 | FAIL |
+------------------+----------+
| Arch Linux | FAIL |
+------------------+----------+
| Fedora 32 | FAIL |
+------------------+----------+
| Fedora 31 | FAIL |
+------------------+----------+
| openSUSE Leap 15 | FAIL |
+------------------+----------+
| CentOS Stream 8 | FAIL |
+------------------+----------+
==== 20 line log output for Ubuntu 18.04 ARM (abi_test): ====
Error: can't find librte_compress_mlx5.dump in build
Error: can't find librte_compress_octeontx.dump in build
Error: can't find librte_compress_zlib.dump in build
Error: can't find librte_regex_mlx5.dump in build
Error: can't find librte_regex_octeontx2.dump in build
Error: can't find librte_vdpa_ifc.dump in build
Error: can't find librte_vdpa_mlx5.dump in build
Error: can't find librte_event_dpaa.dump in build
Error: can't find librte_event_dpaa2.dump in build
Error: can't find librte_event_octeontx2.dump in build
Error: can't find librte_event_opdl.dump in build
Error: can't find librte_event_skeleton.dump in build
Error: can't find librte_event_sw.dump in build
Error: can't find librte_event_dsw.dump in build
Error: can't find librte_event_octeontx.dump in build
Error: can't find librte_baseband_null.dump in build
Error: can't find librte_baseband_turbo_sw.dump in build
Error: can't find librte_baseband_fpga_lte_fec.dump in build
Error: can't find librte_baseband_fpga_5gnr_fec.dump in build
Error: can't find librte_baseband_acc100.dump in build
==== End log output ====
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.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)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.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)
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)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Arch Linux
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.0
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
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
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/16929/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-05-05 0:15 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=20210505001505.E84A48904A@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).