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| pw122297 [PATCH] [v2] eventdev/crypto: fix missing crypto vec limits
Date: Wed, 18 Jan 2023 11:31:47 +0000 (UTC)	[thread overview]
Message-ID: <20230118113147.C8B48601CE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]

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

_Testing PASS_

Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Wednesday, January 18 2023 10:21:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:83397b9f073904438965e1fda2efe76f7850fe01

122297 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| RHEL 7           | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Ubuntu 20.04     | PASS     |
+------------------+----------+


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)

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

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

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

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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-01-18 11:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 11:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-19  6:12 dpdklab
2023-01-19  1:37 dpdklab
2023-01-19  0:52 dpdklab
2023-01-19  0:52 dpdklab
2023-01-19  0:52 dpdklab
2023-01-19  0:52 dpdklab
2023-01-19  0:52 dpdklab
2023-01-19  0:51 dpdklab
2023-01-19  0:51 dpdklab
2023-01-19  0:51 dpdklab
2023-01-18 12:10 dpdklab
2023-01-18 11:29 dpdklab
     [not found] <20230118102148.233481-1-vfialko@marvell.com>
2023-01-18 10:13 ` |SUCCESS| pw122297 [PATCH v2] " qemudev
2023-01-18 10:17 ` qemudev
2023-01-18 10:22 ` checkpatch
2023-01-18 11:19 ` 0-day Robot
2023-01-18 11:09 |SUCCESS| pw122297 [PATCH] [v2] " dpdklab
2023-01-18 11:05 dpdklab
2023-01-18 10:58 dpdklab
2023-01-18 10:56 dpdklab
2023-01-18 10:55 dpdklab
2023-01-18 10:54 dpdklab
2023-01-18 10:53 dpdklab
2023-01-18 10:49 dpdklab
2023-01-18 10:48 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=20230118113147.C8B48601CE@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).