automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| [GIT MASTER] 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
Date: Sun, 15 Sep 2024 18:09:34 -0700 (PDT)	[thread overview]
Message-ID: <66e7854e.050a0220.29fee0.6efcSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: dpdk

41dd9a6bc2d9c6e20e139ad713cc9d172572dd43 --> testing issues

Upstream job id: Generic-DPDK-Compile-ABI#104403

Test environment and result as below:

+-------------------+----------+
|    Environment    | abi_test |
+===================+==========+
| Fedora 39         | FAIL     |
+-------------------+----------+
| CentOS Stream 9   | FAIL     |
+-------------------+----------+
| Fedora 39 (Clang) | FAIL     |
+-------------------+----------+
| Fedora 37         | FAIL     |
+-------------------+----------+
| Fedora 38         | FAIL     |
+-------------------+----------+
| Fedora 38 (Clang) | FAIL     |
+-------------------+----------+
| Debian Bullseye   | FAIL     |
+-------------------+----------+
| Debian 12         | FAIL     |
+-------------------+----------+
| Fedora 40         | FAIL     |
+-------------------+----------+
| openSUSE Leap 15  | FAIL     |
+-------------------+----------+
| RHEL8             | FAIL     |
+-------------------+----------+
| Arch Linux        | FAIL     |
+-------------------+----------+
| Ubuntu 24.04      | FAIL     |
+-------------------+----------+
| RHEL9             | FAIL     |
+-------------------+----------+
| Ubuntu 22.04      | FAIL     |
+-------------------+----------+
| Fedora 40 (Clang) | FAIL     |
+-------------------+----------+

==== 20 line log output for Fedora 40 (Clang) (abi_test): ====
Error: cannot find librte_bus_dpaa.so.24.0 in build_install
Error: cannot find librte_net_memif.so.24.0 in build_install
Error: cannot find librte_common_mlx5.so.24.0 in build_install
Error: cannot find librte_crypto_caam_jr.so.24.0 in build_install
Error: cannot find librte_net_cpfl.so.24.0 in build_install
Error: cannot find librte_baseband_turbo_sw.so.24.0 in build_install
Error: cannot find librte_crypto_dpaa_sec.so.24.0 in build_install
Error: cannot find librte_regex_cn9k.so.24.0 in build_install
Error: cannot find librte_net_vdev_netvsc.so.24.0 in build_install
Error: cannot find librte_common_cpt.so.24.0 in build_install
Error: cannot find librte_event_dpaa2.so.24.0 in build_install
Error: cannot find librte_net_iavf.so.24.0 in build_install
Error: cannot find librte_compress_zlib.so.24.0 in build_install
Error: cannot find librte_net_pfe.so.24.0 in build_install
Error: cannot find librte_baseband_la12xx.so.24.0 in build_install
Error: cannot find librte_bitratestats.so.24.0 in build_install
Error: cannot find librte_net_tap.so.24.0 in build_install
Error: cannot find librte_member.so.24.0 in build_install
Error: cannot find librte_gro.so.24.0 in build_install
Error: cannot find librte_cryptodev.so.24.0 in build_install
==== End log output ====

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

openSUSE Leap 15
	Kernel: Depends on container host
	Compiler: gcc (SUSE Linux) 7.5.0

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Arch Linux
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240805

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30605/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-09-16  1:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  1:09 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-18  3:13 dpdklab
2024-09-18  2:20 dpdklab
2024-09-16  1:04 dpdklab
2024-09-16  1:04 dpdklab
2024-09-14  2:16 dpdklab
2024-09-12  3:38 dpdklab
2024-09-10  4:36 dpdklab
2024-09-10  3:43 dpdklab
2024-09-08  1:28 dpdklab
2024-09-08  0:37 dpdklab
2024-09-06  8:08 dpdklab
2024-09-06  8:01 dpdklab
2024-09-04  1:33 dpdklab
2024-09-04  1:30 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=66e7854e.050a0220.29fee0.6efcSMTPIN_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).