From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140291 [PATCH] [v2] test/crypto: fix enqueue dequeue cal
Date: Thu, 23 May 2024 09:56:42 -0700 (PDT) [thread overview]
Message-ID: <664f754a.170a0220.a4793.14f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240523124838.3474899-1-gakhil@marvell.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140291
_Testing PASS_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Thursday, May 23 2024 12:48:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33
140291 --> 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 |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | 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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.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 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
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29999/
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-23 16:56 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240523124838.3474899-1-gakhil@marvell.com>
2024-05-23 12:22 ` |SUCCESS| pw140291 [PATCH v2] test/crypto: fix enqueue dequeue callback case qemudev
2024-05-23 12:27 ` qemudev
2024-05-23 12:48 ` checkpatch
2024-05-23 13:44 ` 0-day Robot
2024-05-23 16:14 ` |SUCCESS| pw140291 [PATCH] [v2] test/crypto: fix enqueue dequeue cal dpdklab
2024-05-23 16:17 ` dpdklab
2024-05-23 16:18 ` dpdklab
2024-05-23 16:19 ` dpdklab
2024-05-23 16:20 ` dpdklab
2024-05-23 16:49 ` dpdklab
2024-05-23 16:51 ` dpdklab
2024-05-23 16:51 ` dpdklab
2024-05-23 16:52 ` dpdklab
2024-05-23 16:52 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:54 ` dpdklab
2024-05-23 16:54 ` dpdklab
2024-05-23 16:54 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab [this message]
2024-05-23 16:56 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 17:00 ` dpdklab
2024-05-23 17:00 ` dpdklab
2024-05-23 17:00 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:04 ` dpdklab
2024-05-23 17:04 ` dpdklab
2024-05-23 17:05 ` dpdklab
2024-05-23 17:05 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:09 ` dpdklab
2024-05-23 17:10 ` dpdklab
2024-05-23 17:12 ` dpdklab
2024-05-23 17:14 ` dpdklab
2024-05-23 17:15 ` dpdklab
2024-05-23 17:19 ` dpdklab
2024-05-23 17:21 ` dpdklab
2024-05-23 17:21 ` dpdklab
2024-05-23 17:25 ` dpdklab
2024-05-23 17:33 ` dpdklab
2024-05-23 17:36 ` dpdklab
2024-05-23 17:51 ` dpdklab
2024-05-23 17:57 ` dpdklab
2024-05-23 17:57 ` 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=664f754a.170a0220.a4793.14f4SMTPIN_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).