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| pw136092 [PATCH] app/crypto-perf: support TLS record
Date: Wed, 24 Jan 2024 00:59:02 -0800 (PST)	[thread overview]
Message-ID: <65b0d156.050a0220.91641.1732SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Wednesday, January 24 2024 06:49:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:30a988126ecee65a890a4b6a52690442024f2554

136092 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


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

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-24  8:59 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  8:59 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-25  1:03 dpdklab
2024-01-24 23:38 dpdklab
2024-01-24 21:55 dpdklab
2024-01-24 21:54 dpdklab
2024-01-24 21:48 dpdklab
2024-01-24 21:47 dpdklab
2024-01-24 21:45 dpdklab
2024-01-24 21:43 dpdklab
2024-01-24 21:42 dpdklab
2024-01-24 21:40 dpdklab
2024-01-24 21:33 dpdklab
2024-01-24 21:33 dpdklab
2024-01-24 21:33 dpdklab
2024-01-24 21:30 dpdklab
2024-01-24 21:25 dpdklab
2024-01-24 21:23 dpdklab
2024-01-24 21:18 dpdklab
2024-01-24 21:17 dpdklab
2024-01-24 21:17 dpdklab
2024-01-24 21:16 dpdklab
2024-01-24 21:14 dpdklab
2024-01-24 21:13 dpdklab
2024-01-24 21:12 dpdklab
2024-01-24 21:12 dpdklab
2024-01-24 21:12 dpdklab
2024-01-24 21:11 dpdklab
2024-01-24 21:11 dpdklab
2024-01-24 21:10 dpdklab
2024-01-24 21:09 dpdklab
2024-01-24 21:09 dpdklab
2024-01-24 21:09 dpdklab
2024-01-24 21:07 dpdklab
2024-01-24 21:07 dpdklab
2024-01-24 21:06 dpdklab
2024-01-24 21:05 dpdklab
2024-01-24 21:05 dpdklab
2024-01-24 21:03 dpdklab
2024-01-24 21:01 dpdklab
2024-01-24 20:58 dpdklab
2024-01-24 20:58 dpdklab
2024-01-24 20:53 dpdklab
2024-01-24 20:53 dpdklab
2024-01-24 20:50 dpdklab
2024-01-24 19:16 dpdklab
2024-01-24 11:35 dpdklab
2024-01-24 11:34 dpdklab
2024-01-24 10:48 dpdklab
2024-01-24 10:25 dpdklab
2024-01-24 10:06 dpdklab
2024-01-24  9:52 dpdklab
2024-01-24  9:43 dpdklab
2024-01-24  9:22 dpdklab
2024-01-24  9:19 dpdklab
2024-01-24  9:18 dpdklab
2024-01-24  9:14 dpdklab
2024-01-24  9:09 dpdklab
2024-01-24  9:08 dpdklab
2024-01-24  9:06 dpdklab
2024-01-24  9:05 dpdklab
2024-01-24  9:02 dpdklab
2024-01-24  9:00 dpdklab
2024-01-24  9:00 dpdklab
2024-01-24  9:00 dpdklab
2024-01-24  9:00 dpdklab
2024-01-24  9:00 dpdklab
2024-01-24  8:59 dpdklab
2024-01-24  8:59 dpdklab
2024-01-24  8:59 dpdklab
2024-01-24  8:58 dpdklab
2024-01-24  8:58 dpdklab
2024-01-24  8:58 dpdklab
2024-01-24  8:58 dpdklab
2024-01-24  8:58 dpdklab
2024-01-24  8:58 dpdklab
2024-01-24  8:57 dpdklab
2024-01-24  8:57 dpdklab
2024-01-24  8:57 dpdklab
2024-01-24  8:57 dpdklab
2024-01-24  8:57 dpdklab
2024-01-24  8:56 dpdklab
2024-01-24  8:56 dpdklab
2024-01-24  8:56 dpdklab
2024-01-24  8:56 dpdklab
2024-01-24  8:53 dpdklab
2024-01-24  8:52 dpdklab
2024-01-24  8:52 dpdklab
2024-01-24  8:52 dpdklab
2024-01-24  8:51 dpdklab
2024-01-24  8:50 dpdklab
2024-01-24  8:50 dpdklab
2024-01-24  8:49 dpdklab
2024-01-24  8:46 dpdklab
2024-01-24  8:45 dpdklab
2024-01-24  8:32 dpdklab
2024-01-24  8:31 dpdklab
2024-01-24  8:31 dpdklab
2024-01-24  8:22 dpdklab
2024-01-24  8:14 dpdklab
2024-01-24  8:14 dpdklab
2024-01-24  8:10 dpdklab
2024-01-24  8:06 dpdklab
     [not found] <20240124064924.3277434-1-gakhil@marvell.com>
2024-01-24  6:27 ` qemudev
2024-01-24  6:31 ` qemudev
2024-01-24  6:51 ` checkpatch
2024-01-24  7:41 ` 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=65b0d156.050a0220.91641.1732SMTPIN_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).