From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| [GIT MASTER] 9836014d4c2b1b2c29948c928fd386b2944b6bcf
Date: Sun, 06 Aug 2023 18:34:08 -0700 (PDT) [thread overview]
Message-ID: <64d04a10.4a0a0220.7a088.9b4eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: dpdk
9836014d4c2b1b2c29948c928fd386b2944b6bcf --> testing fail
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| openSUSE Leap 15 | FAIL |
+------------------+----------+
| CentOS Stream 9 | FAIL |
+------------------+----------+
| Debian Bullseye | FAIL |
+------------------+----------+
| CentOS Stream 8 | FAIL |
+------------------+----------+
| RHEL8 | FAIL |
+------------------+----------+
| Fedora 38 | FAIL |
+------------------+----------+
| Ubuntu 22.04 | FAIL |
+------------------+----------+
==== 20 line log output for Ubuntu 22.04 (abi_test): ====
Error: cannot find librte_net_idpf.so.23.0 in build_install
Error: cannot find librte_common_idpf.so.23.0 in build_install
Error: cannot find librte_net_gve.so.23.0 in build_install
Error: cannot find librte_crypto_dpaa_sec.so.23.0 in build_install
Error: cannot find librte_event_octeontx.so.23.0 in build_install
Error: cannot find librte_net_af_packet.so.23.0 in build_install
Error: cannot find librte_raw_skeleton.so.23.0 in build_install
Error: cannot find librte_raw_dpaa2_cmdif.so.23.0 in build_install
Error: cannot find librte_net_cnxk.so.23.0 in build_install
Error: cannot find librte_compress_zlib.so.23.0 in build_install
Error: cannot find librte_bus_auxiliary.so.23.0 in build_install
Error: cannot find librte_net_vhost.so.23.0 in build_install
Error: cannot find librte_net_txgbe.so.23.0 in build_install
Error: cannot find librte_dma_idxd.so.23.0 in build_install
Error: cannot find librte_regex_mlx5.so.23.0 in build_install
Error: cannot find librte_event_dpaa.so.23.0 in build_install
Error: cannot find librte_mempool.so.23.0 in build_install
Error: cannot find librte_metrics.so.23.0 in build_install
Error: cannot find librte_gpudev.so.23.0 in build_install
Error: cannot find librte_kvargs.so.23.0 in build_install
==== End log output ====
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25718/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-07 1:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 1:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-08 1:50 dpdklab
2023-08-08 1:50 dpdklab
2023-08-08 1:39 dpdklab
2023-08-08 1:29 dpdklab
2023-08-08 1:20 dpdklab
2023-08-08 1:17 dpdklab
2023-08-07 1:43 dpdklab
2023-08-07 1:43 dpdklab
2023-08-07 1:36 dpdklab
2023-08-07 1:33 dpdklab
2023-08-07 1:31 dpdklab
2023-08-07 1:30 dpdklab
2023-08-07 1:19 dpdklab
2023-08-06 1:40 dpdklab
2023-08-06 1:39 dpdklab
2023-08-06 1:29 dpdklab
2023-08-06 1:29 dpdklab
2023-08-06 1:21 dpdklab
2023-08-06 1:18 dpdklab
2023-08-05 1:54 dpdklab
2023-08-05 1:54 dpdklab
2023-08-05 1:50 dpdklab
2023-08-05 1:49 dpdklab
2023-08-05 1:48 dpdklab
2023-08-05 1:35 dpdklab
2023-08-05 1:34 dpdklab
2023-08-05 1:28 dpdklab
2023-08-05 1:26 dpdklab
2023-08-05 1:25 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=64d04a10.4a0a0220.7a088.9b4eSMTPIN_ADDED_MISSING@mx.google.com \
--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).