From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw143034-143036 [PATCH] [v3,3/3] net/enic: allow multicast
Date: Fri, 09 Aug 2024 04:11:27 -0700 (PDT) [thread overview]
Message-ID: <66b5f95f.050a0220.16c11f.e549SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240809070754.26128-4-hyonkim@cisco.com>
Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/143036
_Testing issues_
Submitter: Hyong Youb Kim <hyonkim@cisco.com>
Date: Friday, August 09 2024 07:07:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b
143034-143036 --> testing issues
Upstream job id: Generic-DPDK-Compile-ABI#102252
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| CentOS Stream 9 | PEND |
+-------------------+----------+
| Debian Bullseye | FAIL |
+-------------------+----------+
| Debian 12 | PEND |
+-------------------+----------+
| Fedora 38 (Clang) | FAIL |
+-------------------+----------+
| Fedora 37 | FAIL |
+-------------------+----------+
| Fedora 40 | FAIL |
+-------------------+----------+
| Fedora 38 | PEND |
+-------------------+----------+
| Fedora 39 | FAIL |
+-------------------+----------+
| Fedora 40 (Clang) | FAIL |
+-------------------+----------+
| Fedora 39 (Clang) | FAIL |
+-------------------+----------+
| openSUSE Leap 15 | FAIL |
+-------------------+----------+
| RHEL9 | FAIL |
+-------------------+----------+
| Ubuntu 22.04 | PEND |
+-------------------+----------+
| Ubuntu 24.04 | PEND |
+-------------------+----------+
==== 20 line log output for RHEL9 (abi_test): ====
Error: cannot find librte_bus_platform.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_common_mlx5.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_cpfl.so.24.0 in build_install
Error: cannot find librte_baseband_turbo_sw.so.24.0 in build_install
Error: cannot find librte_common_cpt.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_vdev_netvsc.so.24.0 in build_install
Error: cannot find librte_compress_zlib.so.24.0 in build_install
Error: cannot find librte_baseband_la12xx.so.24.0 in build_install
Error: cannot find librte_net_pfe.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_member.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
==== 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 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30752/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-08-09 11:11 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809070754.26128-4-hyonkim@cisco.com>
2024-08-09 6:42 ` |SUCCESS| pw143034-143036 [PATCH v3 3/3] net/enic: allow multicast in MAC address add callback qemudev
2024-08-09 6:46 ` qemudev
2024-08-09 7:09 ` |SUCCESS| pw143036 " checkpatch
2024-08-09 8:02 ` 0-day Robot
2024-08-09 9:09 ` |SUCCESS| pw143034-143036 [PATCH] [v3,3/3] net/enic: allow multicast dpdklab
2024-08-09 9:13 ` dpdklab
2024-08-09 9:14 ` dpdklab
2024-08-09 9:16 ` |PENDING| " dpdklab
2024-08-09 9:18 ` |SUCCESS| " dpdklab
2024-08-09 9:18 ` dpdklab
2024-08-09 9:24 ` dpdklab
2024-08-09 9:31 ` dpdklab
2024-08-09 9:32 ` dpdklab
2024-08-09 9:34 ` dpdklab
2024-08-09 10:00 ` dpdklab
2024-08-09 10:44 ` |WARNING| " dpdklab
2024-08-09 10:53 ` |SUCCESS| " dpdklab
2024-08-09 11:01 ` |WARNING| " dpdklab
2024-08-09 11:05 ` dpdklab
2024-08-09 11:06 ` dpdklab
2024-08-09 11:10 ` dpdklab
2024-08-09 11:11 ` dpdklab [this message]
2024-08-09 11:11 ` dpdklab
2024-08-09 11:12 ` dpdklab
2024-08-09 11:14 ` dpdklab
2024-08-09 11:17 ` dpdklab
2024-08-09 11:17 ` dpdklab
2024-08-09 11:19 ` dpdklab
2024-08-09 11:26 ` dpdklab
2024-08-09 11:31 ` |SUCCESS| " dpdklab
2024-08-09 11:37 ` dpdklab
2024-08-09 12:06 ` dpdklab
2024-08-09 12:25 ` |WARNING| " dpdklab
2024-08-09 12:36 ` |SUCCESS| " dpdklab
2024-08-09 12:56 ` dpdklab
2024-08-09 16:09 ` |PENDING| " dpdklab
2024-08-09 16:10 ` dpdklab
2024-08-09 16:14 ` dpdklab
2024-08-09 16:19 ` dpdklab
2024-08-09 16:19 ` dpdklab
2024-08-09 16:23 ` dpdklab
2024-08-09 16:49 ` dpdklab
2024-08-09 18:02 ` dpdklab
2024-08-09 18:06 ` dpdklab
2024-08-09 18:07 ` dpdklab
2024-08-09 18:09 ` dpdklab
2024-08-09 18:10 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:14 ` dpdklab
2024-08-09 18:15 ` dpdklab
2024-08-09 18:16 ` dpdklab
2024-08-09 18:16 ` dpdklab
2024-08-09 18:19 ` dpdklab
2024-08-09 18:19 ` dpdklab
2024-08-09 18:19 ` dpdklab
2024-08-09 18:21 ` dpdklab
2024-08-09 18:21 ` dpdklab
2024-08-09 18:23 ` dpdklab
2024-08-09 18:23 ` dpdklab
2024-08-09 18:24 ` dpdklab
2024-08-09 18:24 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:25 ` dpdklab
2024-08-09 18:26 ` dpdklab
2024-08-09 18:27 ` dpdklab
2024-08-09 18:29 ` dpdklab
2024-08-09 18:29 ` dpdklab
2024-08-09 18:30 ` dpdklab
2024-08-09 18:30 ` dpdklab
2024-08-09 18:32 ` dpdklab
2024-08-09 18:32 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:33 ` dpdklab
2024-08-09 18:37 ` dpdklab
2024-08-09 18:38 ` dpdklab
2024-08-09 18:41 ` dpdklab
2024-08-09 18:42 ` dpdklab
2024-08-09 18:47 ` dpdklab
2024-08-09 18:50 ` dpdklab
2024-08-09 19:02 ` dpdklab
2024-08-09 19:03 ` |SUCCESS| " dpdklab
2024-08-09 19:16 ` |PENDING| " dpdklab
2024-08-09 19:25 ` dpdklab
2024-08-09 19:42 ` dpdklab
2024-08-09 19:45 ` |SUCCESS| " dpdklab
2024-08-09 19:47 ` |PENDING| " dpdklab
2024-08-09 19:53 ` dpdklab
2024-08-09 20:01 ` dpdklab
2024-08-09 21:20 ` dpdklab
2024-08-10 2:03 ` |SUCCESS| " 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=66b5f95f.050a0220.16c11f.e549SMTPIN_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).