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| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar
Date: Wed, 27 Mar 2024 14:27:27 -0700 (PDT)	[thread overview]
Message-ID: <66048f3f.170a0220.1cab5.e18eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1711569406-7750-5-git-send-email-roretzla@linux.microsoft.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138875

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 27 2024 19:56:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ded4d4765171b88470e59307f10625e942f22fca

138873-138875 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian 11 (arm)     | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+


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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

UNH-IOL DPDK Community Lab

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

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

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1711569406-7750-5-git-send-email-roretzla@linux.microsoft.com>
2024-03-27 19:35 ` |SUCCESS| pw138873-138875 [PATCH v8 4/4] cryptodev: remove rte marker fields qemudev
2024-03-27 19:39 ` qemudev
2024-03-27 19:57 ` |SUCCESS| pw138875 " checkpatch
2024-03-27 20:35 ` |SUCCESS| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:35 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:36 ` dpdklab
2024-03-27 20:37 ` dpdklab
2024-03-27 20:37 ` dpdklab
2024-03-27 20:38 ` dpdklab
2024-03-27 20:40 ` |WARNING| " dpdklab
2024-03-27 20:42 ` dpdklab
2024-03-27 20:43 ` |SUCCESS| " dpdklab
2024-03-27 20:44 ` dpdklab
2024-03-27 20:44 ` |WARNING| " dpdklab
2024-03-27 20:44 ` dpdklab
2024-03-27 20:45 ` |FAILURE| pw138875 [PATCH v8 4/4] cryptodev: remove rte marker fields 0-day Robot
2024-03-27 20:45 ` |SUCCESS| pw138873-138875 [PATCH] [v8,4/4] cryptodev: remove rte mar dpdklab
2024-03-27 20:46 ` |WARNING| " dpdklab
2024-03-27 20:47 ` dpdklab
2024-03-27 20:48 ` dpdklab
2024-03-27 20:49 ` |SUCCESS| " dpdklab
2024-03-27 20:52 ` |WARNING| " dpdklab
2024-03-27 20:53 ` dpdklab
2024-03-27 20:56 ` |SUCCESS| " dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:57 ` dpdklab
2024-03-27 20:59 ` dpdklab
2024-03-27 21:00 ` dpdklab
2024-03-27 21:01 ` dpdklab
2024-03-27 21:01 ` dpdklab
2024-03-27 21:03 ` dpdklab
2024-03-27 21:05 ` dpdklab
2024-03-27 21:06 ` dpdklab
2024-03-27 21:06 ` dpdklab
2024-03-27 21:08 ` dpdklab
2024-03-27 21:09 ` dpdklab
2024-03-27 21:09 ` dpdklab
2024-03-27 21:10 ` dpdklab
2024-03-27 21:12 ` dpdklab
2024-03-27 21:12 ` dpdklab
2024-03-27 21:13 ` dpdklab
2024-03-27 21:13 ` dpdklab
2024-03-27 21:16 ` dpdklab
2024-03-27 21:16 ` dpdklab
2024-03-27 21:22 ` dpdklab
2024-03-27 21:24 ` dpdklab
2024-03-27 21:25 ` dpdklab
2024-03-27 21:27 ` dpdklab [this message]
2024-03-27 21:29 ` dpdklab
2024-03-27 21:29 ` dpdklab
2024-03-27 21:30 ` dpdklab
2024-03-27 21:30 ` dpdklab
2024-03-27 21:31 ` dpdklab
2024-03-27 21:31 ` dpdklab
2024-03-27 21:34 ` dpdklab
2024-03-27 21:38 ` dpdklab
2024-03-27 21:38 ` dpdklab
2024-03-27 21:39 ` dpdklab
2024-03-27 21:42 ` dpdklab
2024-03-27 21:42 ` dpdklab
2024-03-27 21:49 ` dpdklab
2024-03-27 21:49 ` dpdklab
2024-03-27 21:52 ` dpdklab
2024-03-27 21:58 ` dpdklab
2024-03-27 22:01 ` dpdklab
2024-03-27 22:02 ` dpdklab
2024-03-27 22:08 ` dpdklab
2024-03-27 22:19 ` dpdklab
2024-03-27 22:21 ` dpdklab
2024-03-27 22:30 ` dpdklab
2024-03-27 22:46 ` dpdklab
2024-03-27 22:58 ` dpdklab
2024-03-27 23:24 ` dpdklab
2024-03-27 23:26 ` dpdklab
2024-03-27 23:28 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-27 23:50 ` dpdklab
2024-03-28  0:06 ` dpdklab
2024-04-02 11:20 ` dpdklab
2024-04-02 11:24 ` dpdklab
2024-04-02 11:28 ` dpdklab
2024-04-02 11:32 ` dpdklab
2024-04-02 11:51 ` 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=66048f3f.170a0220.1cab5.e18eSMTPIN_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).