automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126080 [PATCH] crypto/scheduler: fix last element for valid args
Date: Fri, 14 Apr 2023 21:26:06 +0000 (UTC)	[thread overview]
Message-ID: <20230414212606.305F66008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing PASS_

Submitter: Power, Ciara <ciara.power@intel.com>
Date: Friday, April 14 2023 12:33:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd

126080 --> testing pass

Test environment and result as below:

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


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

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

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

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-14 21:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 21:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-15  8:31 dpdklab
2023-04-15  8:31 dpdklab
2023-04-15  4:33 dpdklab
2023-04-15  4:25 dpdklab
2023-04-15  4:21 dpdklab
2023-04-15  4:00 dpdklab
2023-04-15  1:11 dpdklab
2023-04-14 21:31 dpdklab
2023-04-14 21:28 dpdklab
2023-04-14 21:26 dpdklab
2023-04-14 21:13 dpdklab
2023-04-14 21:11 dpdklab
2023-04-14 21:10 dpdklab
2023-04-14 21:07 dpdklab
2023-04-14 21:07 dpdklab
2023-04-14 21:02 dpdklab
2023-04-14 20:58 dpdklab
2023-04-14 20:14 dpdklab
2023-04-14 20:00 dpdklab
2023-04-14 19:18 dpdklab
2023-04-14 19:10 dpdklab
2023-04-14 19:02 dpdklab
2023-04-14 18:58 dpdklab
2023-04-14 18:58 dpdklab
2023-04-14 18:57 dpdklab
2023-04-14 18:54 dpdklab
2023-04-14 18:49 dpdklab
2023-04-14 18:49 dpdklab
2023-04-14 18:47 dpdklab
     [not found] <20230414123306.575977-1-ciara.power@intel.com>
2023-04-14 12:22 ` qemudev
2023-04-14 12:26 ` qemudev
2023-04-14 12:33 ` checkpatch
2023-04-14 13:39 ` 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=20230414212606.305F66008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).