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| pw143037-143041 [PATCH] [5/5] eal: extend bitops to handle
Date: Fri, 09 Aug 2024 07:05:35 -0700 (PDT)	[thread overview]
Message-ID: <66b6222f.050a0220.3d3ed1.ff23SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240809090439.589295-6-mattias.ronnblom@ericsson.com>

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

_Testing issues_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Friday, August 09 2024 09:04:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143037-143041 --> testing issues

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

Test environment and result as below:

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

==== 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_baseband_turbo_sw.so.24.0 in build_install
Error: cannot find librte_net_cpfl.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_crypto_dpaa_sec.so.24.0 in build_install
Error: cannot find librte_net_iavf.so.24.0 in build_install
Error: cannot find librte_event_dpaa2.so.24.0 in build_install
Error: cannot find librte_net_pfe.so.24.0 in build_install
Error: cannot find librte_compress_zlib.so.24.0 in build_install
Error: cannot find librte_common_cpt.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_gro.so.24.0 in build_install
Error: cannot find librte_bitratestats.so.24.0 in build_install
Error: cannot find librte_member.so.24.0 in build_install
==== End log output ====

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-09 14:05 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240809090439.589295-6-mattias.ronnblom@ericsson.com>
2024-08-09  8:48 ` |SUCCESS| pw143037-143041 [PATCH 5/5] eal: extend bitops to handle volatile pointers qemudev
2024-08-09  8:52 ` qemudev
2024-08-09  9:15 ` |WARNING| pw143041 " checkpatch
2024-08-09 10:02 ` |FAILURE| " 0-day Robot
2024-08-09 10:57 ` |SUCCESS| pw143037-143041 [PATCH] [5/5] eal: extend bitops to handle dpdklab
2024-08-09 11:08 ` |PENDING| " dpdklab
2024-08-09 11:09 ` dpdklab
2024-08-09 11:21 ` |SUCCESS| " dpdklab
2024-08-09 11:22 ` dpdklab
2024-08-09 11:24 ` dpdklab
2024-08-09 11:35 ` dpdklab
2024-08-09 11:36 ` dpdklab
2024-08-09 11:43 ` dpdklab
2024-08-09 11:44 ` dpdklab
2024-08-09 11:59 ` dpdklab
2024-08-09 12:18 ` dpdklab
2024-08-09 13:04 ` dpdklab
2024-08-09 13:09 ` dpdklab
2024-08-09 13:14 ` dpdklab
2024-08-09 13:20 ` dpdklab
2024-08-09 13:40 ` dpdklab
2024-08-09 14:01 ` |WARNING| " dpdklab
2024-08-09 14:04 ` dpdklab
2024-08-09 14:05 ` dpdklab [this message]
2024-08-09 14:06 ` dpdklab
2024-08-09 14:08 ` dpdklab
2024-08-09 14:09 ` dpdklab
2024-08-09 14:11 ` dpdklab
2024-08-09 14:15 ` dpdklab
2024-08-09 14:16 ` dpdklab
2024-08-09 14:18 ` dpdklab
2024-08-09 14:19 ` dpdklab
2024-08-09 14:22 ` dpdklab
2024-08-09 14:24 ` dpdklab
2024-08-09 16:47 ` |FAILURE| " dpdklab
2024-08-09 16:48 ` dpdklab
2024-08-09 17:52 ` dpdklab
2024-08-09 17:56 ` dpdklab
2024-08-09 18:09 ` dpdklab
2024-08-09 18:11 ` dpdklab
2024-08-09 18:17 ` dpdklab
2024-08-09 18:28 ` dpdklab
2024-08-09 18:39 ` dpdklab
2024-08-09 18:41 ` dpdklab
2024-08-09 18:45 ` dpdklab
2024-08-09 18:46 ` dpdklab
2024-08-09 18:47 ` dpdklab
2024-08-09 18:50 ` dpdklab
2024-08-09 18:53 ` dpdklab
2024-08-09 18:57 ` dpdklab
2024-08-09 19:02 ` dpdklab
2024-08-09 19:02 ` dpdklab
2024-08-09 19:04 ` dpdklab
2024-08-09 19:05 ` dpdklab
2024-08-09 19:06 ` dpdklab
2024-08-09 19:06 ` dpdklab
2024-08-09 19:07 ` dpdklab
2024-08-09 19:07 ` dpdklab
2024-08-09 19:08 ` dpdklab
2024-08-09 19:09 ` dpdklab
2024-08-09 19:09 ` dpdklab
2024-08-09 19:10 ` dpdklab
2024-08-09 19:10 ` dpdklab
2024-08-09 19:12 ` dpdklab
2024-08-09 19:22 ` dpdklab
2024-08-09 19:25 ` dpdklab
2024-08-09 19:26 ` dpdklab
2024-08-09 19:27 ` dpdklab
2024-08-09 19:34 ` dpdklab
2024-08-09 19:40 ` dpdklab
2024-08-09 19:41 ` dpdklab
2024-08-09 19:41 ` dpdklab
2024-08-09 19:44 ` dpdklab
2024-08-09 19:54 ` dpdklab
2024-08-09 20:10 ` dpdklab
2024-08-09 20:11 ` dpdklab
2024-08-09 20:12 ` dpdklab
2024-08-09 20:17 ` dpdklab
2024-08-09 20:25 ` dpdklab
2024-08-09 20:32 ` dpdklab
2024-08-09 20:33 ` dpdklab
2024-08-09 20:33 ` dpdklab
2024-08-09 20:38 ` dpdklab
2024-08-09 20:41 ` dpdklab
2024-08-09 21:05 ` dpdklab
2024-08-09 21:15 ` dpdklab
2024-08-10  2:08 ` |WARNING| " 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=66b6222f.050a0220.3d3ed1.ff23SMTPIN_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).