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: [dpdk-test-report] |SUCCESS| pw95972 [PATCH] [v2] crypto/octeontx2: fix lookaside IPsec IV pointer
Date: Mon, 19 Jul 2021 12:15:53 -0400 (EDT)	[thread overview]
Message-ID: <20210719161553.AE20B88E63@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Testing PASS_

Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Friday, July 16 2021 10:44:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:761a321acf9111132f7789ac374e08a7ea7ea0f7

95972 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Ubuntu 20.04 ARM | PASS     |
+------------------+----------+
| Ubuntu 18.04     | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+
| Ubuntu 20.04     | PASS     |
+------------------+----------+
| Arch Linux       | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Fedora 32        | PASS     |
+------------------+----------+
| Fedora 31        | PASS     |
+------------------+----------+
| Fedora 34        | PASS     |
+------------------+----------+
| Fedora 34 clang  | PASS     |
+------------------+----------+
| CentOS 8         | PASS     |
+------------------+----------+


Ubuntu 20.04 ARM
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

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 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

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

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-07-19 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 16:15 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-21  5:37 dpdklab
2021-07-19 19:35 dpdklab
2021-07-19 15:30 dpdklab
2021-07-19 15:13 dpdklab
     [not found] <20210716104447.5313-1-ktejasree@marvell.com>
2021-07-16  9:50 ` [dpdk-test-report] |SUCCESS| pw95972 [PATCH v2] " checkpatch

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=20210719161553.AE20B88E63@noxus.dpdklab.iol.unh.edu \
    --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).