From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126225 [PATCH] ipsec: fix NAT-T length calculation
Date: Tue, 18 Apr 2023 12:10:41 +0000 (UTC) [thread overview]
Message-ID: <20230418121041.6F84760095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126225
_Testing PASS_
Submitter: Xiao Liang <shaw.leon@gmail.com>
Date: Tuesday, April 18 2023 08:46:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126225 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26028/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-18 12:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 12:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-19 0:47 dpdklab
2023-04-19 0:46 dpdklab
2023-04-18 17:01 dpdklab
2023-04-18 16:13 dpdklab
2023-04-18 11:50 dpdklab
2023-04-18 11:49 dpdklab
2023-04-18 11:43 dpdklab
2023-04-18 11:40 dpdklab
2023-04-18 11:39 dpdklab
2023-04-18 11:35 dpdklab
2023-04-18 11:27 dpdklab
2023-04-18 11:20 dpdklab
2023-04-18 11:15 dpdklab
2023-04-18 11:11 dpdklab
2023-04-18 11:08 dpdklab
2023-04-18 10:39 dpdklab
2023-04-18 10:35 dpdklab
2023-04-18 10:31 dpdklab
2023-04-18 10:27 dpdklab
2023-04-18 10:27 dpdklab
2023-04-18 10:27 dpdklab
2023-04-18 10:22 dpdklab
2023-04-18 10:22 dpdklab
2023-04-18 10:20 dpdklab
2023-04-18 10:20 dpdklab
2023-04-18 10:14 dpdklab
2023-04-18 10:13 dpdklab
2023-04-18 10:11 dpdklab
[not found] <20230418084613.52740-1-shaw.leon@gmail.com>
2023-04-18 8:37 ` qemudev
2023-04-18 8:41 ` qemudev
2023-04-18 8:48 ` checkpatch
2023-04-18 9: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=20230418121041.6F84760095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).