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| pw126833-126834 [PATCH] [2/2] crypto/cnxk: fix IPsec CCM capabilities
Date: Fri, 12 May 2023 07:57:49 -0700 (PDT)	[thread overview]
Message-ID: <645e53ed.6b0a0220.6c2fe.567dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Friday, May 12 2023 12:56:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61

126833-126834 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Debian Buster    | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+


Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: clang 14.0.5-1.fc36

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-12 14:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 14:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-12 23:38 dpdklab
2023-05-12 23:33 dpdklab
2023-05-12 23:25 dpdklab
2023-05-12 23:09 dpdklab
2023-05-12 23:04 dpdklab
2023-05-12 16:12 dpdklab
2023-05-12 16:11 dpdklab
2023-05-12 15:45 dpdklab
2023-05-12 15:43 dpdklab
2023-05-12 15:28 dpdklab
2023-05-12 15:09 dpdklab
2023-05-12 15:08 dpdklab
2023-05-12 15:07 dpdklab
2023-05-12 15:04 dpdklab
2023-05-12 15:03 dpdklab
2023-05-12 14:56 dpdklab
2023-05-12 14:53 dpdklab
2023-05-12 14:50 dpdklab
2023-05-12 14:46 dpdklab
2023-05-12 14:42 dpdklab
2023-05-12 14:41 dpdklab
2023-05-12 14:29 dpdklab
2023-05-12 14:28 dpdklab
2023-05-12 14:24 dpdklab
2023-05-12 14:22 dpdklab
2023-05-12 14:22 dpdklab
2023-05-12 14:17 dpdklab
2023-05-12 14:15 dpdklab
     [not found] <20230512125621.1131396-3-ktejasree@marvell.com>
2023-05-12 12:45 ` |SUCCESS| pw126833-126834 [PATCH 2/2] " qemudev
2023-05-12 12:49 ` qemudev

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=645e53ed.6b0a0220.6c2fe.567dSMTPIN_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).