From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135980 [PATCH] [v1] crypto/ipsec_mb: upgrade IPsec Multi
Date: Fri, 19 Jan 2024 09:33:08 -0800 (PST) [thread overview]
Message-ID: <65aab254.810a0220.e278e.47c3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135980
_Testing PASS_
Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Friday, January 19 2024 11:40:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:30a988126ecee65a890a4b6a52690442024f2554
135980 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28909/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-19 17:33 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 17:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 15:05 dpdklab
2024-01-22 14:58 dpdklab
2024-01-19 19:39 dpdklab
2024-01-19 19:33 dpdklab
2024-01-19 18:43 dpdklab
2024-01-19 18:37 dpdklab
2024-01-19 18:31 dpdklab
2024-01-19 18:20 dpdklab
2024-01-19 18:17 dpdklab
2024-01-19 18:04 dpdklab
2024-01-19 17:53 dpdklab
2024-01-19 17:53 dpdklab
2024-01-19 17:53 dpdklab
2024-01-19 17:52 dpdklab
2024-01-19 17:51 dpdklab
2024-01-19 17:33 dpdklab
2024-01-19 17:32 dpdklab
2024-01-19 17:32 dpdklab
2024-01-19 17:31 dpdklab
2024-01-19 17:28 dpdklab
2024-01-19 17:27 dpdklab
2024-01-19 17:27 dpdklab
2024-01-19 17:27 dpdklab
2024-01-19 17:25 dpdklab
2024-01-19 17:25 dpdklab
2024-01-19 17:22 dpdklab
2024-01-19 17:19 dpdklab
2024-01-19 17:17 dpdklab
2024-01-19 17:02 dpdklab
2024-01-19 16:49 dpdklab
2024-01-19 16:49 dpdklab
2024-01-19 16:47 dpdklab
2024-01-19 16:47 dpdklab
2024-01-19 16:46 dpdklab
2024-01-19 16:41 dpdklab
2024-01-19 16:28 dpdklab
2024-01-19 16:25 dpdklab
2024-01-19 16:25 dpdklab
2024-01-19 16:25 dpdklab
2024-01-19 16:24 dpdklab
2024-01-19 16:24 dpdklab
2024-01-19 16:24 dpdklab
2024-01-19 16:23 dpdklab
2024-01-19 16:23 dpdklab
2024-01-19 16:23 dpdklab
2024-01-19 16:22 dpdklab
2024-01-19 16:21 dpdklab
2024-01-19 16:20 dpdklab
2024-01-19 16:19 dpdklab
2024-01-19 16:19 dpdklab
2024-01-19 16:12 dpdklab
2024-01-19 15:47 dpdklab
2024-01-19 15:44 dpdklab
2024-01-19 15:44 dpdklab
2024-01-19 15:44 dpdklab
2024-01-19 15:40 dpdklab
2024-01-19 15:39 dpdklab
2024-01-19 15:36 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=65aab254.810a0220.e278e.47c3SMTPIN_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).