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| pw149412 [PATCH] [v2,1/1] dts: add EAL confidence check su
Date: Mon, 06 Jan 2025 17:43:24 -0800 (PST)	[thread overview]
Message-ID: <677c86bc.170a0220.256cd5.6a7bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241223185739.29621-1-dmarx@iol.unh.edu>

Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/149412

_Testing issues_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Monday, December 23 2024 18:57:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fd51012de5369679e807be1d6a81d63ef15015ce

149412 --> testing issues

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

Test environment and result as below:

+-------------------+----------+
|    Environment    | abi_test |
+===================+==========+
| RHEL8             | PEND     |
+-------------------+----------+
| Ubuntu 24.04      | PEND     |
+-------------------+----------+
| Fedora 40 (Clang) | PEND     |
+-------------------+----------+
| CentOS Stream 9   | FAIL     |
+-------------------+----------+
| Ubuntu 22.04      | PEND     |
+-------------------+----------+
| Debian 12         | PEND     |
+-------------------+----------+
| openSUSE Leap 15  | PEND     |
+-------------------+----------+
| Fedora 41 (Clang) | PEND     |
+-------------------+----------+
| Fedora 41         | PEND     |
+-------------------+----------+
| RHEL9             | PEND     |
+-------------------+----------+

==== 20 line log output for CentOS Stream 9 (abi_test): ====
Error: cannot find librte_net_atlantic.so.24.0 in build_install
Error: cannot find librte_net_memif.so.24.0 in build_install
Error: cannot find librte_crypto_caam_jr.so.24.0 in build_install
Error: cannot find librte_baseband_turbo_sw.so.24.0 in build_install
Error: cannot find librte_net_af_packet.so.24.0 in build_install
Error: cannot find librte_crypto_dpaa_sec.so.24.0 in build_install
Error: cannot find librte_net_vdev_netvsc.so.24.0 in build_install
Error: cannot find librte_event_dpaa2.so.24.0 in build_install
Error: cannot find librte_common_cpt.so.24.0 in build_install
Error: cannot find librte_net_cpfl.so.24.0 in build_install
Error: cannot find librte_compress_zlib.so.24.0 in build_install
Error: cannot find librte_net_iavf.so.24.0 in build_install
Error: cannot find librte_bitratestats.so.24.0 in build_install
Error: cannot find librte_baseband_la12xx.so.24.0 in build_install
Error: cannot find librte_net_tap.so.24.0 in build_install
Error: cannot find librte_cryptodev.so.24.0 in build_install
Error: cannot find librte_regex_cn9k.so.24.0 in build_install
Error: cannot find librte_gro.so.24.0 in build_install
Error: cannot find librte_member.so.24.0 in build_install
Error: cannot find librte_net_pfe.so.24.0 in build_install
==== End log output ====

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

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

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

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

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

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

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

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Fedora 41
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32200/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-01-07  1:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241223185739.29621-1-dmarx@iol.unh.edu>
2024-12-23 17:27 ` |SUCCESS| pw149412 [PATCH v2 1/1] dts: add EAL confidence check suite qemudev
2024-12-23 17:32 ` qemudev
2024-12-23 17:56 ` checkpatch
2024-12-23 18:45 ` 0-day Robot
2024-12-23 20:33 ` |SUCCESS| pw149412 [PATCH] [v2,1/1] dts: add EAL confidence check su dpdklab
2024-12-23 20:44 ` dpdklab
2024-12-23 20:55 ` dpdklab
2024-12-23 20:56 ` dpdklab
2024-12-23 21:16 ` dpdklab
2024-12-23 21:20 ` dpdklab
2024-12-23 21:35 ` |PENDING| " dpdklab
2024-12-23 21:41 ` |SUCCESS| " dpdklab
2024-12-23 21:45 ` |PENDING| " dpdklab
2024-12-23 21:50 ` |SUCCESS| " dpdklab
2024-12-23 22:07 ` dpdklab
2024-12-23 22:38 ` |WARNING| " dpdklab
2024-12-23 22:39 ` dpdklab
2024-12-23 23:12 ` dpdklab
2024-12-23 23:53 ` |SUCCESS| " dpdklab
2024-12-24  0:10 ` dpdklab
2024-12-25 11:47 ` dpdklab
2025-01-07  1:43 ` dpdklab [this message]
2025-01-07  2:36 ` |WARNING| " dpdklab
2025-01-08 17:32 ` |PENDING| " 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=677c86bc.170a0220.256cd5.6a7bSMTPIN_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).