From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136256 [PATCH] [v2] test/security: add inline IPsec Rx i
Date: Thu, 01 Feb 2024 05:48:32 -0800 (PST) [thread overview]
Message-ID: <65bba130.630a0220.f646f.f1cfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136256
_Testing PASS_
Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Thursday, February 01 2024 10:07:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2b551097b3443ebf662e4d140600a4c9b108e73c
136256 --> 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 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29014/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 13:48 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 13:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 16:07 dpdklab
2024-02-01 15:33 dpdklab
2024-02-01 15:16 dpdklab
2024-02-01 15:11 dpdklab
2024-02-01 15:10 dpdklab
2024-02-01 15:08 dpdklab
2024-02-01 14:53 dpdklab
2024-02-01 14:52 dpdklab
2024-02-01 14:46 dpdklab
2024-02-01 14:46 dpdklab
2024-02-01 14:41 dpdklab
2024-02-01 14:35 dpdklab
2024-02-01 14:29 dpdklab
2024-02-01 14:28 dpdklab
2024-02-01 14:27 dpdklab
2024-02-01 14:26 dpdklab
2024-02-01 14:25 dpdklab
2024-02-01 14:25 dpdklab
2024-02-01 14:24 dpdklab
2024-02-01 14:23 dpdklab
2024-02-01 14:22 dpdklab
2024-02-01 14:22 dpdklab
2024-02-01 14:22 dpdklab
2024-02-01 14:20 dpdklab
2024-02-01 14:20 dpdklab
2024-02-01 14:20 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:19 dpdklab
2024-02-01 14:18 dpdklab
2024-02-01 14:18 dpdklab
2024-02-01 14:17 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:15 dpdklab
2024-02-01 14:08 dpdklab
2024-02-01 14:07 dpdklab
2024-02-01 14:06 dpdklab
2024-02-01 14:06 dpdklab
2024-02-01 14:05 dpdklab
2024-02-01 14:05 dpdklab
2024-02-01 14:05 dpdklab
2024-02-01 14:03 dpdklab
2024-02-01 14:01 dpdklab
2024-02-01 14:01 dpdklab
2024-02-01 13:59 dpdklab
2024-02-01 13:59 dpdklab
2024-02-01 13:57 dpdklab
2024-02-01 13:55 dpdklab
2024-02-01 13:54 dpdklab
2024-02-01 13:53 dpdklab
2024-02-01 13:53 dpdklab
2024-02-01 13:52 dpdklab
2024-02-01 13:52 dpdklab
2024-02-01 13:52 dpdklab
2024-02-01 13:51 dpdklab
2024-02-01 13:50 dpdklab
2024-02-01 13:48 dpdklab
2024-02-01 13:47 dpdklab
2024-02-01 13:47 dpdklab
2024-02-01 13:46 dpdklab
2024-02-01 13:33 dpdklab
2024-02-01 13:33 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=65bba130.630a0220.f646f.f1cfSMTPIN_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).