From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137997-138000 [PATCH] [v5,4/4] crypto/ipsec_mb: unified
Date: Tue, 05 Mar 2024 10:24:12 -0800 (PST) [thread overview]
Message-ID: <65e7634c.170a0220.71836.1e12SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240305174227.1785111-4-brian.dooley@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138000
_Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Tuesday, March 05 2024 17:42:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:240fcef51bceb527c624a2329ca1e3030fbd64db
137997-138000 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| FreeBSD 13.2 | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29424/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-05 18:24 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305174227.1785111-4-brian.dooley@intel.com>
2024-03-05 17:20 ` |SUCCESS| pw137997-138000 [PATCH v5 4/4] crypto/ipsec_mb: unified IPsec MB interface qemudev
2024-03-05 17:24 ` qemudev
2024-03-05 17:43 ` |SUCCESS| pw138000 " checkpatch
2024-03-05 18:24 ` dpdklab [this message]
2024-03-05 18:24 ` |SUCCESS| pw137997-138000 [PATCH] [v5,4/4] crypto/ipsec_mb: unified dpdklab
2024-03-05 18:30 ` dpdklab
2024-03-05 18:31 ` dpdklab
2024-03-05 18:33 ` dpdklab
2024-03-05 18:34 ` dpdklab
2024-03-05 18:42 ` dpdklab
2024-03-05 18:45 ` |FAILURE| pw138000 [PATCH v5 4/4] crypto/ipsec_mb: unified IPsec MB interface 0-day Robot
2024-03-05 18:45 ` |SUCCESS| pw137997-138000 [PATCH] [v5,4/4] crypto/ipsec_mb: unified dpdklab
2024-03-05 18:52 ` dpdklab
2024-03-05 18:56 ` |WARNING| " dpdklab
2024-03-05 18:57 ` |SUCCESS| " dpdklab
2024-03-05 19:02 ` dpdklab
2024-03-05 19:03 ` dpdklab
2024-03-05 19:04 ` dpdklab
2024-03-05 19:04 ` dpdklab
2024-03-05 19:05 ` dpdklab
2024-03-05 19:07 ` |WARNING| " dpdklab
2024-03-05 19:07 ` |SUCCESS| " dpdklab
2024-03-05 19:12 ` dpdklab
2024-03-05 19:13 ` dpdklab
2024-03-05 19:14 ` |WARNING| " dpdklab
2024-03-05 19:14 ` |SUCCESS| " dpdklab
2024-03-05 19:15 ` dpdklab
2024-03-05 19:16 ` |WARNING| " dpdklab
2024-03-05 19:16 ` |SUCCESS| " dpdklab
2024-03-05 19:18 ` |WARNING| " dpdklab
2024-03-05 19:18 ` |SUCCESS| " dpdklab
2024-03-05 19:18 ` dpdklab
2024-03-05 19:19 ` |WARNING| " dpdklab
2024-03-05 19:20 ` |SUCCESS| " dpdklab
2024-03-05 19:20 ` dpdklab
2024-03-05 19:20 ` dpdklab
2024-03-05 19:21 ` dpdklab
2024-03-05 19:21 ` |WARNING| " dpdklab
2024-03-05 19:22 ` |SUCCESS| " dpdklab
2024-03-05 19:22 ` dpdklab
2024-03-05 19:23 ` dpdklab
2024-03-05 19:26 ` dpdklab
2024-03-05 19:27 ` dpdklab
2024-03-05 19:28 ` dpdklab
2024-03-05 19:29 ` |WARNING| " dpdklab
2024-03-05 19:30 ` |SUCCESS| " dpdklab
2024-03-05 19:33 ` dpdklab
2024-03-05 19:35 ` dpdklab
2024-03-05 19:38 ` dpdklab
2024-03-05 19:38 ` dpdklab
2024-03-05 19:39 ` dpdklab
2024-03-05 19:39 ` dpdklab
2024-03-05 19:42 ` dpdklab
2024-03-05 19:51 ` dpdklab
2024-03-05 19:53 ` dpdklab
2024-03-05 19:54 ` |WARNING| " dpdklab
2024-03-05 19:55 ` |SUCCESS| " dpdklab
2024-03-05 19:55 ` dpdklab
2024-03-05 19:55 ` dpdklab
2024-03-05 19:56 ` dpdklab
2024-03-05 19:58 ` dpdklab
2024-03-05 20:00 ` dpdklab
2024-03-05 20:01 ` dpdklab
2024-03-05 20:02 ` dpdklab
2024-03-05 20:05 ` dpdklab
2024-03-05 20:08 ` dpdklab
2024-03-05 20:23 ` dpdklab
2024-03-05 20:25 ` dpdklab
2024-03-05 21:21 ` dpdklab
2024-03-05 22:01 ` dpdklab
2024-03-06 0:11 ` |WARNING| " dpdklab
2024-03-06 0:22 ` dpdklab
2024-03-09 21:34 ` |SUCCESS| " dpdklab
2024-03-09 22:10 ` dpdklab
2024-03-09 23:04 ` dpdklab
2024-03-15 19:11 ` dpdklab
2024-03-15 19:14 ` dpdklab
2024-03-15 19:15 ` dpdklab
2024-03-15 19:24 ` dpdklab
2024-03-15 19:24 ` dpdklab
2024-03-15 19:25 ` |WARNING| " dpdklab
2024-03-15 19:27 ` dpdklab
2024-03-15 19:29 ` |SUCCESS| " dpdklab
2024-03-15 19:35 ` dpdklab
2024-03-15 19:38 ` dpdklab
2024-03-15 19:38 ` |WARNING| " dpdklab
2024-03-15 19:40 ` dpdklab
2024-03-15 19:41 ` |SUCCESS| " dpdklab
2024-03-15 19:44 ` dpdklab
2024-03-15 19:47 ` dpdklab
2024-03-15 19:49 ` |WARNING| " dpdklab
2024-03-15 19:50 ` dpdklab
2024-03-15 19:54 ` |SUCCESS| " dpdklab
2024-03-15 20:09 ` |WARNING| " dpdklab
2024-03-15 20:14 ` dpdklab
2024-03-15 20:16 ` |SUCCESS| " dpdklab
2024-03-15 20:22 ` dpdklab
2024-03-15 20:38 ` 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=65e7634c.170a0220.71836.1e12SMTPIN_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).