From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw120915 [PATCH] [v2] examples/ipsec-secgw: set AES-CTR IV length to 16
Date: Thu, 15 Dec 2022 08:53:35 +0000 (UTC) [thread overview]
Message-ID: <20221215085335.5DC036008E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/120915
_Testing PASS_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Thursday, December 15 2022 05:42:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c581c49cd3fcaff596fbe566e270b442e6326c79
120915 --> testing pass
Test environment and result as below:
+-------------------------------+----------------+--------------------+----------------------+
| Environment | dpdk_unit_test | dpdk_meson_compile | dpdk_mingw64_compile |
+===============================+================+====================+======================+
| Ubuntu 20.04 ARM GCC Native | PASS | SKIPPED | SKIPPED |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM Clang Native | PASS | SKIPPED | SKIPPED |
+-------------------------------+----------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS | PASS |
+-------------------------------+----------------+--------------------+----------------------+
| RHEL 7 | PASS | SKIPPED | SKIPPED |
+-------------------------------+----------------+--------------------+----------------------+
| FreeBSD 13 | SKIPPED | PASS | SKIPPED |
+-------------------------------+----------------+--------------------+----------------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24743/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-15 8:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 8:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-15 10:40 dpdklab
2022-12-15 9:46 dpdklab
2022-12-15 9:18 dpdklab
2022-12-15 9:18 dpdklab
2022-12-15 9:14 dpdklab
2022-12-15 9:10 dpdklab
2022-12-15 9:09 dpdklab
2022-12-15 8:59 dpdklab
2022-12-15 8:59 dpdklab
2022-12-15 8:59 dpdklab
2022-12-15 8:58 dpdklab
2022-12-15 8:58 dpdklab
2022-12-15 7:06 dpdklab
2022-12-15 6:57 dpdklab
2022-12-15 6:50 dpdklab
2022-12-15 6:42 dpdklab
2022-12-15 6:34 dpdklab
2022-12-15 6:21 dpdklab
2022-12-15 6:18 dpdklab
2022-12-15 6:10 dpdklab
[not found] <20221215054211.1919093-1-ktejasree@marvell.com>
2022-12-15 5:33 ` |SUCCESS| pw120915 [PATCH v2] " qemudev
2022-12-15 5:37 ` qemudev
2022-12-15 5:43 ` checkpatch
2022-12-15 6:39 ` 0-day Robot
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=20221215085335.5DC036008E@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).