automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141153 [PATCH] [v2,1/1] crypto/ipsec_mb: unify some IPse
Date: Fri, 14 Jun 2024 16:44:11 -0700 (PDT)	[thread overview]
Message-ID: <666cd5cb.050a0220.790da.5f9dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240614140759.1123505-2-brian.dooley@intel.com>

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141153

_Testing PASS_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Friday, June 14 2024 14:07:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6909b48776badc05542a410ebd34bcfec4c248bf

141153 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Fedora 39        | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Debian 12        | PASS     |
+------------------+----------+
| Fedora 37        | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| RHEL9            | PASS     |
+------------------+----------+
| Fedora 40        | PASS     |
+------------------+----------+


CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Fedora 40
	Kernel: Depends on container host
	Compiler: clang 18.1.6

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30193/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-06-14 23:44 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240614140759.1123505-2-brian.dooley@intel.com>
2024-06-14 13:47 ` |SUCCESS| pw141153 [PATCH v2 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs qemudev
2024-06-14 13:51 ` qemudev
2024-06-14 14:09 ` checkpatch
2024-06-14 15:04 ` 0-day Robot
2024-06-14 22:09 ` |SUCCESS| pw141153 [PATCH] [v2,1/1] crypto/ipsec_mb: unify some IPse dpdklab
2024-06-14 22:13 ` dpdklab
2024-06-14 22:19 ` dpdklab
2024-06-14 22:20 ` dpdklab
2024-06-14 22:24 ` dpdklab
2024-06-14 22:34 ` dpdklab
2024-06-14 22:57 ` dpdklab
2024-06-14 23:05 ` dpdklab
2024-06-14 23:19 ` dpdklab
2024-06-14 23:20 ` dpdklab
2024-06-14 23:20 ` dpdklab
2024-06-14 23:22 ` dpdklab
2024-06-14 23:22 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:24 ` dpdklab
2024-06-14 23:24 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:43 ` dpdklab
2024-06-14 23:43 ` dpdklab
2024-06-14 23:44 ` dpdklab [this message]
2024-06-14 23:44 ` dpdklab
2024-06-14 23:45 ` dpdklab
2024-06-14 23:46 ` dpdklab
2024-06-14 23:46 ` dpdklab
2024-06-14 23:46 ` dpdklab
2024-06-14 23:47 ` dpdklab
2024-06-14 23:48 ` dpdklab
2024-06-14 23:48 ` dpdklab
2024-06-14 23:50 ` dpdklab
2024-06-14 23:51 ` dpdklab
2024-06-14 23:52 ` dpdklab
2024-06-14 23:53 ` dpdklab
2024-06-14 23:54 ` dpdklab
2024-06-14 23:54 ` dpdklab
2024-06-15  0:08 ` dpdklab
2024-06-15  0:12 ` dpdklab
2024-06-15  0:27 ` dpdklab
2024-06-15  0:54 ` dpdklab
2024-06-15  0:55 ` dpdklab
2024-06-15  0:56 ` dpdklab
2024-06-15  0:56 ` dpdklab
2024-06-15  0:59 ` dpdklab
2024-06-15  1:00 ` dpdklab
2024-06-15  1:01 ` dpdklab
2024-06-15  1:01 ` dpdklab
2024-06-15  1:01 ` dpdklab
2024-06-15  1:02 ` dpdklab
2024-06-15  1:04 ` dpdklab
2024-06-15  1:06 ` dpdklab
2024-06-15  1:08 ` dpdklab
2024-06-15  1:08 ` dpdklab
2024-06-15  1:09 ` dpdklab
2024-06-15  1:09 ` dpdklab
2024-06-15  1:10 ` dpdklab
2024-06-15  1:13 ` dpdklab
2024-06-15  1:16 ` dpdklab
2024-06-15  1:17 ` dpdklab
2024-06-15  1:18 ` dpdklab
2024-06-15  1:20 ` dpdklab
2024-06-15  1:23 ` dpdklab
2024-06-15  1:25 ` dpdklab
2024-06-15  1:26 ` dpdklab
2024-06-15  1:26 ` dpdklab
2024-06-15  1:26 ` dpdklab
2024-06-15  1:26 ` dpdklab
2024-06-15  1:27 ` dpdklab
2024-06-15  1:27 ` dpdklab
2024-06-15  1:28 ` dpdklab
2024-06-15  1:29 ` dpdklab
2024-06-15  1:30 ` dpdklab
2024-06-15  1:30 ` dpdklab
2024-06-15  1:30 ` dpdklab
2024-06-15  1:32 ` dpdklab
2024-06-15  1:35 ` dpdklab
2024-06-15  1:37 ` dpdklab
2024-06-15  1:38 ` dpdklab
2024-06-15  1:41 ` dpdklab
2024-06-15  1:41 ` dpdklab
2024-06-15  1:43 ` dpdklab
2024-06-15  1:48 ` dpdklab
2024-06-15  1:52 ` dpdklab
2024-06-15  1:55 ` dpdklab
2024-06-15  1:56 ` dpdklab
2024-06-15  2:02 ` dpdklab
2024-06-15  2:02 ` dpdklab
2024-06-15  2:03 ` dpdklab
2024-06-15  2:09 ` dpdklab
2024-06-15  2:10 ` dpdklab
2024-06-15  2:11 ` dpdklab
2024-06-15  2:12 ` dpdklab
2024-06-15  2:14 ` dpdklab
2024-06-15  2:16 ` dpdklab
2024-06-15  2:17 ` dpdklab
2024-06-15  2:18 ` dpdklab
2024-06-15  2:24 ` dpdklab
2024-06-15  2:32 ` dpdklab
2024-06-15  2:34 ` dpdklab
2024-06-15  2:35 ` dpdklab
2024-06-15  2:40 ` dpdklab
2024-06-15  2:41 ` dpdklab
2024-06-15  2:42 ` dpdklab
2024-06-15  2:45 ` dpdklab
2024-06-15  2:47 ` dpdklab
2024-06-15  2:49 ` dpdklab
2024-06-15  2:54 ` dpdklab
2024-06-15  3:07 ` dpdklab
2024-06-15  3:07 ` 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=666cd5cb.050a0220.790da.5f9dSMTPIN_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).