From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135331-135332 [PATCH] [2/2] examples/ipsec-secgw: update
Date: Tue, 19 Dec 2023 00:26:51 -0800 (PST) [thread overview]
Message-ID: <658153cb.050a0220.9288d.2a9dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135332
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Tuesday, December 19 2023 05:29:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135331-135332 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28681/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-19 8:26 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 8:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 11:37 dpdklab
2023-12-19 9:24 dpdklab
2023-12-19 9:11 dpdklab
2023-12-19 8:59 dpdklab
2023-12-19 8:57 dpdklab
2023-12-19 8:55 dpdklab
2023-12-19 8:55 dpdklab
2023-12-19 8:50 dpdklab
2023-12-19 8:49 dpdklab
2023-12-19 8:48 dpdklab
2023-12-19 8:45 dpdklab
2023-12-19 8:43 dpdklab
2023-12-19 8:42 dpdklab
2023-12-19 8:41 dpdklab
2023-12-19 8:40 dpdklab
2023-12-19 8:37 dpdklab
2023-12-19 8:36 dpdklab
2023-12-19 8:35 dpdklab
2023-12-19 8:35 dpdklab
2023-12-19 8:34 dpdklab
2023-12-19 8:33 dpdklab
2023-12-19 8:33 dpdklab
2023-12-19 8:31 dpdklab
2023-12-19 8:31 dpdklab
2023-12-19 8:29 dpdklab
2023-12-19 8:25 dpdklab
2023-12-19 8:24 dpdklab
2023-12-19 8:21 dpdklab
2023-12-19 8:20 dpdklab
2023-12-19 8:18 dpdklab
2023-12-19 8:13 dpdklab
2023-12-19 8:13 dpdklab
2023-12-19 8:11 dpdklab
2023-12-19 8:08 dpdklab
2023-12-19 8:07 dpdklab
2023-12-19 8:06 dpdklab
2023-12-19 8:06 dpdklab
2023-12-19 8:06 dpdklab
2023-12-19 8:04 dpdklab
2023-12-19 8:03 dpdklab
2023-12-19 8:00 dpdklab
2023-12-19 7:58 dpdklab
2023-12-19 7:57 dpdklab
2023-12-19 7:19 dpdklab
2023-12-19 7:15 dpdklab
2023-12-19 7:03 dpdklab
2023-12-19 7:01 dpdklab
2023-12-19 7:01 dpdklab
2023-12-19 7:00 dpdklab
2023-12-19 6:58 dpdklab
2023-12-19 6:58 dpdklab
2023-12-19 6:58 dpdklab
2023-12-19 6:56 dpdklab
2023-12-19 6:51 dpdklab
2023-12-19 6:51 dpdklab
2023-12-19 6:50 dpdklab
2023-12-19 6:50 dpdklab
2023-12-19 6:48 dpdklab
2023-12-19 6:48 dpdklab
2023-12-19 6:48 dpdklab
2023-12-19 6:46 dpdklab
2023-12-19 6:45 dpdklab
2023-12-19 6:45 dpdklab
2023-12-19 6:44 dpdklab
2023-12-19 6:42 dpdklab
2023-12-19 6:42 dpdklab
2023-12-19 6:42 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=658153cb.050a0220.9288d.2a9dSMTPIN_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).