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| pw149201-149207 [PATCH] [v2,7/7] dts: update linters in do
Date: Tue, 07 Jan 2025 09:28:03 -0800 (PST)	[thread overview]
Message-ID: <677d6423.050a0220.1c6766.adf6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241212140013.17548-8-luca.vizzarro@arm.com>

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

_Testing issues_

Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Thursday, December 12 2024 14:00:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7df61db6c387703a36306c1aea92225921e2eeb2

149201-149207 --> testing issues

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

Test environment and result as below:

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

==== 20 line log output for Ubuntu 24.04 (abi_test): ====
Error: cannot find librte_pipeline.so.24.0 in build_install
Error: cannot find librte_net_memif.so.24.0 in build_install
Error: cannot find librte_cryptodev.so.24.0 in build_install
Error: cannot find librte_cfgfile.so.24.0 in build_install
Error: cannot find librte_eal.so.24.0 in build_install
Error: cannot find librte_dmadev.so.24.0 in build_install
Error: cannot find librte_ethdev.so.24.0 in build_install
Error: cannot find librte_net_dpaa2.so.24.0 in build_install
Error: cannot find librte_mbuf.so.24.0 in build_install
Error: cannot find librte_kvargs.so.24.0 in build_install
Error: cannot find librte_pcapng.so.24.0 in build_install
Error: cannot find librte_bpf.so.24.0 in build_install
Error: cannot find librte_cmdline.so.24.0 in build_install
Error: cannot find librte_pdump.so.24.0 in build_install
Error: cannot find librte_eventdev.so.24.0 in build_install
Error: cannot find librte_mempool.so.24.0 in build_install
Error: cannot find librte_member.so.24.0 in build_install
Error: cannot find librte_jobstats.so.24.0 in build_install
Error: cannot find librte_ring.so.24.0 in build_install
Error: cannot find librte_security.so.24.0 in build_install
==== End log output ====

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

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

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

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

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

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

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)

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

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

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

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

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 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241212140013.17548-8-luca.vizzarro@arm.com>
2024-12-12 13:39 ` |SUCCESS| pw149201-149207 [PATCH v2 7/7] dts: update linters in doc page qemudev
2024-12-12 13:44 ` qemudev
2024-12-12 14:05 ` |SUCCESS| pw149207 " checkpatch
2024-12-12 15:03 ` 0-day Robot
2024-12-14 19:02 ` |SUCCESS| pw149201-149207 [PATCH] [v2,7/7] dts: update linters in do dpdklab
2024-12-14 19:12 ` dpdklab
2024-12-14 19:17 ` dpdklab
2024-12-14 19:18 ` dpdklab
2024-12-14 19:19 ` dpdklab
2024-12-14 19:29 ` dpdklab
2024-12-14 19:43 ` dpdklab
2024-12-14 19:57 ` |PENDING| " dpdklab
2024-12-14 20:20 ` |SUCCESS| " dpdklab
2024-12-14 20:44 ` |WARNING| " dpdklab
2024-12-14 22:12 ` |SUCCESS| " dpdklab
2024-12-14 23:53 ` dpdklab
2024-12-14 23:57 ` dpdklab
2024-12-15  0:12 ` dpdklab
2024-12-15  0:20 ` dpdklab
2024-12-15  0:37 ` dpdklab
2024-12-15  1:57 ` |WARNING| " dpdklab
2024-12-15  1:59 ` dpdklab
2024-12-15  2:08 ` |SUCCESS| " dpdklab
2024-12-17  0:15 ` |WARNING| " dpdklab
2025-01-07 16:27 ` dpdklab
2025-01-07 17:28 ` dpdklab [this message]
2025-01-09  3:37 ` 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=677d6423.050a0220.1c6766.adf6SMTPIN_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).