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| pw137425 [PATCH] [v1] eventdev/crypto: fix enqueueing inva
Date: Wed, 28 Feb 2024 08:10:31 -0800 (PST)	[thread overview]
Message-ID: <65df5af7.170a0220.63408.6200SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228103919.2018017-1-ganapati.kundapura@intel.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137425

_Testing PASS_

Submitter: Ganapati Kundapura <ganapati.kundapura@intel.com>
Date: Wednesday, February 28 2024 10:39:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:29cba188385e8c961bfb21690d0eda36f50277e1

137425 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

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

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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-28 16:10 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228103919.2018017-1-ganapati.kundapura@intel.com>
2024-02-28 10:21 ` |SUCCESS| pw137425 [PATCH v1] eventdev/crypto: fix enqueueing invalid ops qemudev
2024-02-28 10:25 ` qemudev
2024-02-28 10:39 ` checkpatch
2024-02-28 11:45 ` 0-day Robot
2024-02-28 13:41 ` |SUCCESS| pw137425 [PATCH] [v1] eventdev/crypto: fix enqueueing inva dpdklab
2024-02-28 13:43 ` dpdklab
2024-02-28 13:44 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:09 ` dpdklab
2024-02-28 14:10 ` dpdklab
2024-02-28 14:10 ` dpdklab
2024-02-28 14:29 ` dpdklab
2024-02-28 14:30 ` dpdklab
2024-02-28 14:33 ` dpdklab
2024-02-28 14:33 ` dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:42 ` dpdklab
2024-02-28 14:42 ` dpdklab
2024-02-28 14:42 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:46 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:47 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:48 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:53 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 15:17 ` dpdklab
2024-02-28 15:20 ` dpdklab
2024-02-28 16:10 ` dpdklab [this message]
2024-02-28 18:16 ` dpdklab
2024-02-28 20:09 ` dpdklab
2024-02-28 20:17 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 23:04 ` dpdklab
2024-02-29 23:06 ` dpdklab
2024-02-29 23:08 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-03-01 20:09 ` dpdklab
2024-03-01 21:03 ` dpdklab
2024-03-01 21:34 ` 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=65df5af7.170a0220.63408.6200SMTPIN_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).