From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137452 [PATCH] crypto/ipsec_mb: update Arm IPsec-MB libr
Date: Wed, 28 Feb 2024 12:38:32 -0800 (PST) [thread overview]
Message-ID: <65df99c8.050a0220.122f0.0f38SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228175250.340922-1-wathsala.vithanage@arm.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137452
_Testing PASS_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Wednesday, February 28 2024 17:52:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137452 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29320/
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-02-28 20:38 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228175250.340922-1-wathsala.vithanage@arm.com>
2024-02-28 17:33 ` |SUCCESS| pw137452 [PATCH] crypto/ipsec_mb: update Arm IPsec-MB library tag qemudev
2024-02-28 17:37 ` qemudev
2024-02-28 17:57 ` checkpatch
2024-02-28 18:45 ` 0-day Robot
2024-02-28 19:43 ` |SUCCESS| pw137452 [PATCH] crypto/ipsec_mb: update Arm IPsec-MB libr dpdklab
2024-02-28 19:50 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:51 ` dpdklab
2024-02-28 19:52 ` dpdklab
2024-02-28 19:57 ` dpdklab
2024-02-28 20:00 ` dpdklab
2024-02-28 20:02 ` dpdklab
2024-02-28 20:03 ` dpdklab
2024-02-28 20:06 ` dpdklab
2024-02-28 20:07 ` dpdklab
2024-02-28 20:09 ` dpdklab
2024-02-28 20:11 ` dpdklab
2024-02-28 20:14 ` dpdklab
2024-02-28 20:16 ` dpdklab
2024-02-28 20:16 ` dpdklab
2024-02-28 20:17 ` dpdklab
2024-02-28 20:17 ` dpdklab
2024-02-28 20:17 ` dpdklab
2024-02-28 20:18 ` dpdklab
2024-02-28 20:20 ` dpdklab
2024-02-28 20:21 ` dpdklab
2024-02-28 20:21 ` dpdklab
2024-02-28 20:21 ` dpdklab
2024-02-28 20:24 ` dpdklab
2024-02-28 20:24 ` dpdklab
2024-02-28 20:25 ` dpdklab
2024-02-28 20:25 ` dpdklab
2024-02-28 20:27 ` dpdklab
2024-02-28 20:27 ` dpdklab
2024-02-28 20:28 ` dpdklab
2024-02-28 20:29 ` dpdklab
2024-02-28 20:29 ` dpdklab
2024-02-28 20:29 ` dpdklab
2024-02-28 20:30 ` dpdklab
2024-02-28 20:30 ` dpdklab
2024-02-28 20:30 ` dpdklab
2024-02-28 20:30 ` dpdklab
2024-02-28 20:31 ` dpdklab
2024-02-28 20:31 ` dpdklab
2024-02-28 20:31 ` dpdklab
2024-02-28 20:31 ` dpdklab
2024-02-28 20:32 ` dpdklab
2024-02-28 20:32 ` dpdklab
2024-02-28 20:32 ` dpdklab
2024-02-28 20:32 ` dpdklab
2024-02-28 20:32 ` dpdklab
2024-02-28 20:34 ` dpdklab
2024-02-28 20:35 ` dpdklab
2024-02-28 20:35 ` dpdklab
2024-02-28 20:35 ` dpdklab
2024-02-28 20:35 ` dpdklab
2024-02-28 20:35 ` dpdklab
2024-02-28 20:36 ` dpdklab
2024-02-28 20:36 ` dpdklab
2024-02-28 20:38 ` dpdklab
2024-02-28 20:38 ` dpdklab [this message]
2024-02-28 20:38 ` dpdklab
2024-02-28 20:39 ` dpdklab
2024-02-28 21:19 ` dpdklab
2024-02-28 21:52 ` dpdklab
2024-02-28 22:57 ` dpdklab
2024-02-28 23:09 ` dpdklab
2024-02-29 22:26 ` dpdklab
2024-03-01 0:57 ` dpdklab
2024-03-01 1:00 ` dpdklab
2024-03-01 1:03 ` dpdklab
2024-03-01 1:07 ` dpdklab
2024-03-02 5:20 ` dpdklab
2024-03-02 5:53 ` dpdklab
2024-03-02 6:25 ` 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=65df99c8.050a0220.122f0.0f38SMTPIN_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).