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| pw120357 [PATCH] [v1] eventdev/crypto: add all failed events to circular buffer
Date: Fri,  2 Dec 2022 11:46:27 +0000 (UTC)	[thread overview]
Message-ID: <20221202114627.0755660091@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Testing PASS_

Submitter: Kundapura, Ganapati <ganapati.kundapura@intel.com>
Date: Wednesday, November 30 2022 15:49:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f262f16087ea6a77357a915cf4c0d10ddc7b6562

120357 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+----------------+
|              Environment               | dpdk_meson_compile | dpdk_unit_test |
+========================================+====================+================+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               | SKIPPED        |
+----------------------------------------+--------------------+----------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               | SKIPPED        |
+----------------------------------------+--------------------+----------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               | SKIPPED        |
+----------------------------------------+--------------------+----------------+
| Ubuntu 20.04 ARM GCC Native            | PASS               | PASS           |
+----------------------------------------+--------------------+----------------+
| Ubuntu 20.04 ARM Clang Native          | PASS               | PASS           |
+----------------------------------------+--------------------+----------------+
| Ubuntu 20.04 ARM SVE                   | PASS               | SKIPPED        |
+----------------------------------------+--------------------+----------------+
| Windows Server 2019                    | SKIPPED            | PASS           |
+----------------------------------------+--------------------+----------------+
| CentOS Stream 8                        | SKIPPED            | PASS           |
+----------------------------------------+--------------------+----------------+
| CentOS Stream 9                        | SKIPPED            | PASS           |
+----------------------------------------+--------------------+----------------+
| Debian Buster                          | SKIPPED            | PASS           |
+----------------------------------------+--------------------+----------------+
| Debian Bullseye                        | SKIPPED            | PASS           |
+----------------------------------------+--------------------+----------------+
| Ubuntu 22.04                           | SKIPPED            | PASS           |
+----------------------------------------+--------------------+----------------+


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

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

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

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

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

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

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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 Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-12-02 11:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 11:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-03  4:03 dpdklab
2022-12-02 13:34 dpdklab
2022-12-02 13:34 dpdklab
2022-12-02 13:03 dpdklab
2022-12-02 12:35 dpdklab
2022-12-02 12:21 dpdklab
2022-12-02 12:11 dpdklab
2022-12-02 11:15 dpdklab
2022-12-02 10:50 dpdklab
2022-12-02 10:22 dpdklab
2022-12-02  9:56 dpdklab
2022-12-02  9:31 dpdklab
2022-12-02  9:16 dpdklab
2022-11-30 18:21 dpdklab
2022-11-30 17:49 dpdklab
2022-11-30 17:22 dpdklab
2022-11-30 17:05 dpdklab
2022-11-30 17:02 dpdklab
2022-11-30 16:58 dpdklab
2022-11-30 16:32 dpdklab
2022-11-30 16:20 dpdklab
     [not found] <20221130154938.1698236-1-ganapati.kundapura@intel.com>
2022-11-30 15:43 ` |SUCCESS| pw120357 [PATCH v1] " qemudev
2022-11-30 15:47 ` qemudev
2022-11-30 15:50 ` checkpatch
2022-11-30 16:58 ` 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=20221202114627.0755660091@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).