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| pw135007 [PATCH] examples/ipsec-secgw: fix cryptodev to SA
Date: Mon, 11 Dec 2023 07:12:34 -0800 (PST)	[thread overview]
Message-ID: <657726e2.170a0220.959c6.b77fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Monday, December 11 2023 09:53:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

135007 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-11 15:12 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 15:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11 17:14 dpdklab
2023-12-11 16:46 dpdklab
2023-12-11 15:59 dpdklab
2023-12-11 15:58 dpdklab
2023-12-11 15:57 dpdklab
2023-12-11 15:57 dpdklab
2023-12-11 15:56 dpdklab
2023-12-11 15:54 dpdklab
2023-12-11 15:53 dpdklab
2023-12-11 15:46 dpdklab
2023-12-11 15:45 dpdklab
2023-12-11 15:45 dpdklab
2023-12-11 15:45 dpdklab
2023-12-11 15:45 dpdklab
2023-12-11 15:44 dpdklab
2023-12-11 15:44 dpdklab
2023-12-11 15:44 dpdklab
2023-12-11 15:44 dpdklab
2023-12-11 15:40 dpdklab
2023-12-11 15:40 dpdklab
2023-12-11 15:39 dpdklab
2023-12-11 15:27 dpdklab
2023-12-11 15:19 dpdklab
2023-12-11 15:18 dpdklab
2023-12-11 15:16 dpdklab
2023-12-11 15:16 dpdklab
2023-12-11 15:15 dpdklab
2023-12-11 15:15 dpdklab
2023-12-11 15:14 dpdklab
2023-12-11 15:13 dpdklab
2023-12-11 15:13 dpdklab
2023-12-11 15:13 dpdklab
2023-12-11 15:12 dpdklab
2023-12-11 15:12 dpdklab
2023-12-11 15:10 dpdklab
2023-12-11 15:09 dpdklab
2023-12-11 15:07 dpdklab
2023-12-11 15:05 dpdklab
2023-12-11 15:04 dpdklab
2023-12-11 15:03 dpdklab
2023-12-11 15:03 dpdklab
2023-12-11 15:02 dpdklab
2023-12-11 15:02 dpdklab
2023-12-11 14:58 dpdklab
2023-12-11 14:55 dpdklab
2023-12-11 14:55 dpdklab
2023-12-11 14:54 dpdklab
2023-12-11 14:54 dpdklab
2023-12-11 14:54 dpdklab
2023-12-11 14:54 dpdklab
2023-12-11 14:53 dpdklab
2023-12-11 14:52 dpdklab
2023-12-11 14:51 dpdklab
2023-12-11 14:51 dpdklab
2023-12-11 14:51 dpdklab
2023-12-11 14:50 dpdklab
2023-12-11 14:50 dpdklab
2023-12-11 14:48 dpdklab
2023-12-11 14:47 dpdklab
2023-12-11 14:47 dpdklab
2023-12-11 14:43 dpdklab
2023-12-11 14:42 dpdklab
2023-12-11 14:40 dpdklab
2023-12-11 14:40 dpdklab
2023-12-11 14:39 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=657726e2.170a0220.959c6.b77fSMTPIN_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).