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| pw137344-137346 [PATCH] [v5,4/4] test/cryptodev: add tests
Date: Tue, 27 Feb 2024 13:04:01 -0800 (PST)	[thread overview]
Message-ID: <65de4e41.630a0220.cd44b.46e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227113345.863082-5-nishikanta.nayak@intel.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137346

_Testing PASS_

Submitter: Nishikant Nayak <nishikanta.nayak@intel.com>
Date: Tuesday, February 27 2024 11:33:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137344-137346 --> testing pass

Test environment and result as below:

+------------------+--------------------+
|   Environment    | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13.2     | PASS               |
+------------------+--------------------+
| CentOS Stream 8  | PASS               |
+------------------+--------------------+
| CentOS Stream 9  | PASS               |
+------------------+--------------------+
| Debian Bullseye  | PASS               |
+------------------+--------------------+
| openSUSE Leap 15 | PASS               |
+------------------+--------------------+
| RHEL8            | PASS               |
+------------------+--------------------+
| Fedora 38        | PASS               |
+------------------+--------------------+
| Fedora 37        | PASS               |
+------------------+--------------------+
| Ubuntu 22.04     | PASS               |
+------------------+--------------------+
| Alpine           | PASS               |
+------------------+--------------------+
| Ubuntu 20.04     | PASS               |
+------------------+--------------------+
| Debian 12 (arm)  | PASS               |
+------------------+--------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.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)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-27 21:04 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227113345.863082-5-nishikanta.nayak@intel.com>
2024-02-27 11:11 ` |SUCCESS| pw137344-137346 [PATCH v5 4/4] test/cryptodev: add tests for GCM with AAD qemudev
2024-02-27 11:16 ` qemudev
2024-02-27 11:35 ` |SUCCESS| pw137346 " checkpatch
2024-02-27 12:25 ` 0-day Robot
2024-02-27 20:52 ` |SUCCESS| pw137344-137346 [PATCH] [v5,4/4] test/cryptodev: add tests dpdklab
2024-02-27 20:53 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:02 ` dpdklab
2024-02-27 21:02 ` dpdklab
2024-02-27 21:02 ` dpdklab
2024-02-27 21:02 ` dpdklab
2024-02-27 21:02 ` dpdklab
2024-02-27 21:02 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:04 ` dpdklab [this message]
2024-02-27 21:05 ` dpdklab
2024-02-27 21:06 ` dpdklab
2024-02-27 21:17 ` dpdklab
2024-02-27 21:17 ` dpdklab
2024-02-27 21:17 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:19 ` dpdklab
2024-02-27 21:20 ` dpdklab
2024-02-27 21:20 ` dpdklab
2024-02-27 21:20 ` dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:35 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 23:13 ` dpdklab
2024-02-28  3:54 ` dpdklab
2024-02-28  8:06 ` dpdklab
2024-02-28  8:09 ` dpdklab
2024-02-28 11:04 ` dpdklab
2024-02-28 20:11 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:38 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-27 17:54 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 17:33 dpdklab
2024-02-27 17:32 dpdklab
2024-02-27 17:31 dpdklab
2024-02-27 17:25 dpdklab
2024-02-27 17:19 dpdklab
2024-02-27 17:12 dpdklab
2024-02-27 16:53 dpdklab
2024-02-27 16:53 dpdklab
2024-02-27 16:52 dpdklab
2024-02-27 16:39 dpdklab
2024-02-27 16:34 dpdklab
2024-02-27 16:32 dpdklab
2024-02-27 16:25 dpdklab
2024-02-27 16:21 dpdklab
2024-02-27 16:09 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=65de4e41.630a0220.cd44b.46e5SMTPIN_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).