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| pw126838 [PATCH] test/crypto: remove redundant code
Date: Fri, 12 May 2023 11:04:41 -0700 (PDT)	[thread overview]
Message-ID: <645e7fb9.810a0220.5b202.ee8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Friday, May 12 2023 14:21:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d03446724972d2a1bb645ce7f3e64f5ef0203d61

126838 --> testing pass

Test environment and result as below:

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


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

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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.1-2

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

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

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

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

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 18:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 18:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-13  2:10 dpdklab
2023-05-13  2:06 dpdklab
2023-05-13  2:01 dpdklab
2023-05-13  1:53 dpdklab
2023-05-13  1:38 dpdklab
2023-05-12 20:23 dpdklab
2023-05-12 20:23 dpdklab
2023-05-12 20:01 dpdklab
2023-05-12 19:20 dpdklab
2023-05-12 18:20 dpdklab
2023-05-12 18:20 dpdklab
2023-05-12 18:20 dpdklab
2023-05-12 18:16 dpdklab
2023-05-12 18:02 dpdklab
2023-05-12 17:59 dpdklab
2023-05-12 17:56 dpdklab
2023-05-12 17:54 dpdklab
2023-05-12 17:52 dpdklab
2023-05-12 17:52 dpdklab
2023-05-12 17:49 dpdklab
2023-05-12 17:42 dpdklab
2023-05-12 17:41 dpdklab
2023-05-12 17:17 dpdklab
2023-05-12 17:05 dpdklab
2023-05-12 17:04 dpdklab
2023-05-12 16:58 dpdklab
2023-05-12 16:58 dpdklab
2023-05-12 16:57 dpdklab
2023-05-12 16:52 dpdklab
2023-05-12 16:52 dpdklab
     [not found] <20230512142148.262-1-anoobj@marvell.com>
2023-05-12 14:22 ` checkpatch
2023-05-12 14:33 ` qemudev
2023-05-12 14:38 ` qemudev
2023-05-12 15:19 ` 0-day Robot

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=645e7fb9.810a0220.5b202.ee8fSMTPIN_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).