From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140342 [PATCH] eal: speed up dpdk init time
Date: Tue, 28 May 2024 02:08:27 -0700 (PDT) [thread overview]
Message-ID: <66559f0b.d40a0220.c32f5.3d51SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240528061259.29528-1-changfengnan@bytedance.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140342
_Testing PASS_
Submitter: Fengnan Chang <changfengnan@bytedance.com>
Date: Tuesday, May 28 2024 06:12:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:77e63757d2a0106a0cc519f5a82e2d749d16475a
140342 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.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
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30026/
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-28 9:08 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528061259.29528-1-changfengnan@bytedance.com>
2024-05-28 5:48 ` qemudev
2024-05-28 5:52 ` qemudev
2024-05-28 6:14 ` |WARNING| " checkpatch
2024-05-28 7:03 ` |SUCCESS| " 0-day Robot
2024-05-28 7:29 ` dpdklab
2024-05-28 7:31 ` dpdklab
2024-05-28 7:36 ` dpdklab
2024-05-28 7:36 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:45 ` dpdklab
2024-05-28 7:45 ` dpdklab
2024-05-28 7:48 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:51 ` dpdklab
2024-05-28 7:52 ` dpdklab
2024-05-28 7:52 ` dpdklab
2024-05-28 7:53 ` dpdklab
2024-05-28 7:53 ` dpdklab
2024-05-28 7:54 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:56 ` dpdklab
2024-05-28 7:56 ` dpdklab
2024-05-28 7:57 ` dpdklab
2024-05-28 7:58 ` dpdklab
2024-05-28 7:58 ` dpdklab
2024-05-28 8:00 ` dpdklab
2024-05-28 8:02 ` dpdklab
2024-05-28 8:33 ` dpdklab
2024-05-28 8:34 ` dpdklab
2024-05-28 8:55 ` dpdklab
2024-05-28 8:56 ` dpdklab
2024-05-28 8:57 ` dpdklab
2024-05-28 8:58 ` dpdklab
2024-05-28 9:01 ` dpdklab
2024-05-28 9:01 ` dpdklab
2024-05-28 9:03 ` dpdklab
2024-05-28 9:08 ` dpdklab [this message]
2024-05-28 10:48 ` dpdklab
2024-05-30 1:01 ` dpdklab
2024-05-30 1:01 ` dpdklab
2024-05-30 1:03 ` 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=66559f0b.d40a0220.c32f5.3d51SMTPIN_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).