From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140298 [PATCH] [v3] net/cpfl: get running host ID for CP
Date: Fri, 24 May 2024 01:46:01 -0700 (PDT) [thread overview]
Message-ID: <665053c9.170a0220.4dd4d.03ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240524040553.487093-1-shaiq.wani@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140298
_Testing PASS_
Submitter: Shaiq Wani <shaiq.wani@intel.com>
Date: Friday, May 24 2024 04:05:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:19be1a0ba8af8a513adb011a3017d583d6312fc9
140298 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30002/
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-05-24 8:46 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240524040553.487093-1-shaiq.wani@intel.com>
2024-05-24 3:40 ` |SUCCESS| pw140298 [PATCH v3] net/cpfl: get running host ID for CPFL PMD qemudev
2024-05-24 3:45 ` qemudev
2024-05-24 4:06 ` |WARNING| " checkpatch
2024-05-24 5:04 ` |SUCCESS| " 0-day Robot
2024-05-24 6:20 ` |SUCCESS| pw140298 [PATCH] [v3] net/cpfl: get running host ID for CP dpdklab
2024-05-24 6:21 ` dpdklab
2024-05-24 6:25 ` dpdklab
2024-05-24 6:42 ` dpdklab
2024-05-24 6:49 ` dpdklab
2024-05-24 6:49 ` dpdklab
2024-05-24 6:56 ` dpdklab
2024-05-24 7:08 ` dpdklab
2024-05-24 7:09 ` dpdklab
2024-05-24 7:13 ` dpdklab
2024-05-24 7:13 ` dpdklab
2024-05-24 7:13 ` dpdklab
2024-05-24 7:14 ` dpdklab
2024-05-24 7:14 ` dpdklab
2024-05-24 8:06 ` dpdklab
2024-05-24 8:07 ` dpdklab
2024-05-24 8:10 ` dpdklab
2024-05-24 8:16 ` dpdklab
2024-05-24 8:17 ` dpdklab
2024-05-24 8:21 ` dpdklab
2024-05-24 8:22 ` dpdklab
2024-05-24 8:24 ` dpdklab
2024-05-24 8:28 ` dpdklab
2024-05-24 8:28 ` dpdklab
2024-05-24 8:30 ` dpdklab
2024-05-24 8:30 ` dpdklab
2024-05-24 8:30 ` dpdklab
2024-05-24 8:31 ` dpdklab
2024-05-24 8:32 ` dpdklab
2024-05-24 8:33 ` dpdklab
2024-05-24 8:33 ` dpdklab
2024-05-24 8:35 ` dpdklab
2024-05-24 8:36 ` dpdklab
2024-05-24 8:36 ` dpdklab
2024-05-24 8:38 ` dpdklab
2024-05-24 8:46 ` dpdklab [this message]
2024-05-24 8:46 ` dpdklab
2024-05-24 8:47 ` dpdklab
2024-05-24 8:49 ` dpdklab
2024-05-24 8:49 ` dpdklab
2024-05-24 8:50 ` dpdklab
2024-05-24 8:51 ` dpdklab
2024-05-24 8:51 ` dpdklab
2024-05-24 8:52 ` dpdklab
2024-05-24 8:52 ` dpdklab
2024-05-24 8:53 ` dpdklab
2024-05-24 8:54 ` dpdklab
2024-05-24 8:54 ` dpdklab
2024-05-24 8:54 ` dpdklab
2024-05-24 8:55 ` dpdklab
2024-05-24 9:04 ` dpdklab
2024-05-24 9:04 ` dpdklab
2024-05-24 9:06 ` dpdklab
2024-05-24 9:07 ` dpdklab
2024-05-24 9:07 ` dpdklab
2024-05-24 9:08 ` dpdklab
2024-05-24 9:10 ` dpdklab
2024-05-24 9:10 ` dpdklab
2024-05-24 9:10 ` dpdklab
2024-05-24 9:13 ` dpdklab
2024-05-24 9:13 ` dpdklab
2024-05-24 9:14 ` dpdklab
2024-05-24 9:15 ` dpdklab
2024-05-24 9:16 ` dpdklab
2024-05-24 9:17 ` dpdklab
2024-05-24 9:17 ` dpdklab
2024-05-24 9:17 ` dpdklab
2024-05-24 9:19 ` dpdklab
2024-05-24 9:19 ` dpdklab
2024-05-24 9:20 ` dpdklab
2024-05-24 9:21 ` dpdklab
2024-05-24 9:22 ` dpdklab
2024-05-24 9:32 ` dpdklab
2024-05-24 9:32 ` dpdklab
2024-05-24 9:32 ` dpdklab
2024-05-24 9:33 ` dpdklab
2024-05-24 9:33 ` dpdklab
2024-05-24 9:40 ` dpdklab
2024-05-24 9:43 ` dpdklab
2024-05-24 9:46 ` dpdklab
2024-05-24 9:55 ` dpdklab
2024-05-24 9:57 ` dpdklab
2024-05-24 10:04 ` dpdklab
2024-05-24 10:52 ` dpdklab
2024-05-24 10:58 ` dpdklab
2024-05-24 11:10 ` 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=665053c9.170a0220.4dd4d.03ffSMTPIN_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).