From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| [GIT MASTER] 0ae35eceb9e4569b0814fcf671b4455301bb7518
Date: Mon, 31 Jul 2023 18:21:10 -0700 (PDT) [thread overview]
Message-ID: <64c85e06.810a0220.37e5a.119aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: dpdk
0ae35eceb9e4569b0814fcf671b4455301bb7518 --> testing fail
Test environment and result as below:
+--------------+----------+
| Environment | abi_test |
+==============+==========+
| Ubuntu 22.04 | FAIL |
+--------------+----------+
| RHEL8 | FAIL |
+--------------+----------+
| Fedora 38 | FAIL |
+--------------+----------+
==== 20 line log output for Fedora 38 (abi_test): ====
Error: cannot find librte_rawdev.so.23.0 in build_install
Error: cannot find librte_pdump.so.23.0 in build_install
Error: cannot find librte_lpm.so.23.0 in build_install
Error: cannot find librte_distributor.so.23.0 in build_install
Error: cannot find librte_net.so.23.0 in build_install
Error: cannot find librte_node.so.23.0 in build_install
Error: cannot find librte_latencystats.so.23.0 in build_install
Error: cannot find librte_bpf.so.23.0 in build_install
Error: cannot find librte_member.so.23.0 in build_install
Error: cannot find librte_stack.so.23.0 in build_install
Error: cannot find librte_gpudev.so.23.0 in build_install
Error: cannot find librte_meter.so.23.0 in build_install
Error: cannot find librte_telemetry.so.23.0 in build_install
Error: cannot find librte_pci.so.23.0 in build_install
Error: cannot find librte_sched.so.23.0 in build_install
Error: cannot find librte_rcu.so.23.0 in build_install
Error: cannot find librte_reorder.so.23.0 in build_install
Error: cannot find librte_pcapng.so.23.0 in build_install
Error: cannot find librte_vhost.so.23.0 in build_install
Error: cannot find librte_ring.so.23.0 in build_install
==== End log output ====
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
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: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25655/
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-01 1:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 1:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-03 2:12 dpdklab
2023-08-03 2:06 dpdklab
2023-08-03 2:06 dpdklab
2023-08-03 1:55 dpdklab
2023-08-03 1:55 dpdklab
2023-08-03 1:54 dpdklab
2023-08-03 1:39 dpdklab
2023-08-03 1:38 dpdklab
2023-08-02 2:06 dpdklab
2023-08-02 2:06 dpdklab
2023-08-02 2:05 dpdklab
2023-08-02 1:51 dpdklab
2023-08-02 1:44 dpdklab
2023-08-02 1:42 dpdklab
2023-08-02 1:39 dpdklab
2023-08-02 1:38 dpdklab
2023-08-02 1:37 dpdklab
2023-08-02 1:24 dpdklab
2023-08-01 2:00 dpdklab
2023-08-01 2:00 dpdklab
2023-08-01 1:42 dpdklab
2023-08-01 1:39 dpdklab
2023-08-01 1:33 dpdklab
2023-08-01 1:33 dpdklab
2023-08-01 1:25 dpdklab
2023-08-01 1:19 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=64c85e06.810a0220.37e5a.119aSMTPIN_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).