automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Ciara Power <ciara.power@intel.com>
Subject: |SUCCESS| pw126893-126900 [PATCH] [v2, 8/8] crypto/ipsec_mb: set and use session ID
Date: Tue, 16 May 2023 10:16:01 -0700 (PDT)	[thread overview]
Message-ID: <6463ba51.170a0220.33c5a.da3aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Ciara Power <ciara.power@intel.com>
Date: Tuesday, May 16 2023 15:24:22 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

126893-126900 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| Ubuntu 22.04    | PASS     |
+-----------------+----------+
| CentOS Stream 8 | PASS     |
+-----------------+----------+
| RHEL 7          | PASS     |
+-----------------+----------+
| CentOS Stream 9 | PASS     |
+-----------------+----------+
| Debian Buster   | PASS     |
+-----------------+----------+
| Debian Bullseye | PASS     |
+-----------------+----------+


Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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)

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-16 17:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 17:16 dpdklab [this message]
     [not found] <20230516152422.606617-9-ciara.power@intel.com>
2023-05-17  3:07 ` |SUCCESS| pw126893-126900 [PATCH v2 " qemudev
2023-05-17  3:07 ` qemudev
  -- strict thread matches above, loose matches on Subject: below --
2023-05-17  2:14 |SUCCESS| pw126893-126900 [PATCH] [v2, " dpdklab
2023-05-17  2:10 dpdklab
2023-05-17  2:00 dpdklab
2023-05-17  1:56 dpdklab
2023-05-17  1:41 dpdklab
2023-05-16 21:05 dpdklab
2023-05-16 21:05 dpdklab
2023-05-16 18:30 dpdklab
2023-05-16 18:06 dpdklab
2023-05-16 18:02 dpdklab
2023-05-16 17:37 dpdklab
2023-05-16 17:31 dpdklab
2023-05-16 17:25 dpdklab
2023-05-16 17:18 dpdklab
2023-05-16 17:17 dpdklab
2023-05-16 17:15 dpdklab
2023-05-16 17:12 dpdklab
2023-05-16 17:10 dpdklab
2023-05-16 17:00 dpdklab
2023-05-16 16:52 dpdklab
2023-05-16 16:46 dpdklab
2023-05-16 16:42 dpdklab
2023-05-16 16:40 dpdklab
2023-05-16 16:34 dpdklab
2023-05-16 16:33 dpdklab
2023-05-16 16:33 dpdklab
2023-05-16 16:32 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=6463ba51.170a0220.33c5a.da3aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=ciara.power@intel.com \
    --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).