From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw151136 [PATCH] [v5] net: add thread-safe crc api
Date: Sat, 08 Feb 2025 01:18:55 -0800 (PST) [thread overview]
Message-ID: <67a7217f.170a0220.2c4760.f481SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250207182443.9775-1-arkadiuszx.kusztal@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/151136
_Testing PASS_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Friday, February 07 2025 18:24:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7125636162d67b1c40ba6802a3ff4466d125d243
151136 --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#359431
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| RHEL9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Fedora 41 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 41 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: Depends on container host
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
Fedora 41 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Ubuntu 20.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04 (ARM)
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
CentOS Stream 9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Debian 11 (Buster) (ARM)
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: Depends on container host
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: Depends on container host
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32530/
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:[~2025-02-08 9:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250207182443.9775-1-arkadiuszx.kusztal@intel.com>
2025-02-07 17:51 ` |SUCCESS| pw151136 [PATCH v5] " qemudev
2025-02-07 17:55 ` qemudev
2025-02-07 18:25 ` |WARNING| " checkpatch
2025-02-07 20:25 ` |SUCCESS| " 0-day Robot
2025-02-08 0:11 ` |SUCCESS| pw151136 [PATCH] [v5] " dpdklab
2025-02-08 0:17 ` dpdklab
2025-02-08 0:37 ` dpdklab
2025-02-08 0:46 ` dpdklab
2025-02-08 1:45 ` dpdklab
2025-02-08 1:56 ` |PENDING| " dpdklab
2025-02-08 2:24 ` dpdklab
2025-02-08 2:29 ` |SUCCESS| " dpdklab
2025-02-08 2:57 ` dpdklab
2025-02-08 3:00 ` |PENDING| " dpdklab
2025-02-08 4:13 ` |SUCCESS| " dpdklab
2025-02-08 4:15 ` dpdklab
2025-02-08 4:55 ` dpdklab
2025-02-08 5:10 ` |PENDING| " dpdklab
2025-02-08 5:33 ` |SUCCESS| " dpdklab
2025-02-08 6:05 ` dpdklab
2025-02-08 6:40 ` dpdklab
2025-02-08 9:14 ` dpdklab
2025-02-08 9:18 ` dpdklab [this message]
2025-02-08 9:21 ` 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=67a7217f.170a0220.2c4760.f481SMTPIN_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).