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| pw142217 [PATCH] driver: crypto: scheduler: fix session si
Date: Mon, 08 Jul 2024 22:15:09 -0700 (PDT)	[thread overview]
Message-ID: <668cc75d.050a0220.77b9d.2e02SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240705125756.227677-1-jhascoet@kalrayinc.com>

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

_Testing PASS_

Submitter: jhascoet <ju.hascoet@gmail.com>
Date: Friday, July 05 2024 12:57:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ba268b0bb43b56174e3d9345a27e6b1675a5a991

142217 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-09  5:15 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240705125756.227677-1-jhascoet@kalrayinc.com>
2024-07-08 12:55 ` |SUCCESS| pw142217 [PATCH] driver: crypto: scheduler: fix session size computation qemudev
2024-07-08 13:00 ` qemudev
2024-07-08 13:13 ` checkpatch
2024-07-09  1:28 ` |PENDING| pw142217 [PATCH] driver: crypto: scheduler: fix session si dpdklab
2024-07-09  1:33 ` dpdklab
2024-07-09  1:37 ` |SUCCESS| " dpdklab
2024-07-09  1:40 ` dpdklab
2024-07-09  1:41 ` dpdklab
2024-07-09  1:45 ` dpdklab
2024-07-09  1:47 ` dpdklab
2024-07-09  1:59 ` dpdklab
2024-07-09  3:05 ` |PENDING| " dpdklab
2024-07-09  3:12 ` |SUCCESS| " dpdklab
2024-07-09  3:48 ` dpdklab
2024-07-09  4:30 ` |PENDING| " dpdklab
2024-07-09  4:33 ` dpdklab
2024-07-09  4:35 ` dpdklab
2024-07-09  4:39 ` dpdklab
2024-07-09  4:41 ` dpdklab
2024-07-09  4:44 ` dpdklab
2024-07-09  4:46 ` dpdklab
2024-07-09  4:48 ` |SUCCESS| " dpdklab
2024-07-09  4:56 ` |PENDING| " dpdklab
2024-07-09  4:58 ` dpdklab
2024-07-09  5:00 ` dpdklab
2024-07-09  5:03 ` dpdklab
2024-07-09  5:06 ` dpdklab
2024-07-09  5:06 ` dpdklab
2024-07-09  5:07 ` dpdklab
2024-07-09  5:09 ` dpdklab
2024-07-09  5:15 ` dpdklab [this message]
2024-07-09  5:16 ` dpdklab
2024-07-09  5:24 ` dpdklab
2024-07-09  5:26 ` dpdklab
2024-07-09  5:32 ` dpdklab
2024-07-09  5:34 ` dpdklab
2024-07-09  5:51 ` dpdklab
2024-07-09  5:55 ` dpdklab
2024-07-09  5:59 ` |SUCCESS| " dpdklab
2024-07-09  7:01 ` |PENDING| " dpdklab
2024-07-09  7:01 ` dpdklab
2024-07-09  7:14 ` dpdklab
2024-07-09  7:15 ` dpdklab
2024-07-09  7:17 ` dpdklab
2024-07-09  7:19 ` dpdklab
2024-07-09  7:25 ` dpdklab
2024-07-09  7:32 ` dpdklab
2024-07-09  7:33 ` dpdklab
2024-07-09  7:41 ` dpdklab
2024-07-09  7:43 ` dpdklab
2024-07-09  7:45 ` dpdklab
2024-07-09  7:46 ` dpdklab
2024-07-09  7:54 ` dpdklab
2024-07-09  7:55 ` dpdklab
2024-07-09  7:57 ` dpdklab
2024-07-09  8:00 ` dpdklab
2024-07-09  8:12 ` |SUCCESS| " dpdklab
2024-07-09  8:58 ` |PENDING| " dpdklab
2024-07-09  9:09 ` dpdklab
2024-07-09  9:10 ` dpdklab
2024-07-09  9:13 ` dpdklab
2024-07-09  9:15 ` dpdklab
2024-07-09  9:17 ` dpdklab
2024-07-09  9:19 ` dpdklab
2024-07-09  9:20 ` dpdklab
2024-07-09  9:21 ` dpdklab
2024-07-09  9:27 ` dpdklab
2024-07-09  9:33 ` dpdklab
2024-07-09  9:37 ` dpdklab
2024-07-09  9:39 ` dpdklab
2024-07-09  9:41 ` dpdklab
2024-07-09  9:45 ` dpdklab
2024-07-09  9:45 ` dpdklab
2024-07-09  9:49 ` dpdklab
2024-07-09  9:51 ` dpdklab
2024-07-09 10:07 ` dpdklab
2024-07-09 10:07 ` dpdklab
2024-07-09 10:20 ` |SUCCESS| " dpdklab
2024-07-09 11:15 ` |PENDING| " dpdklab
2024-07-09 11:19 ` dpdklab
2024-07-09 12:09 ` dpdklab
2024-07-09 12:20 ` dpdklab
2024-07-09 12:26 ` dpdklab
2024-07-09 12:34 ` dpdklab
2024-07-09 12:46 ` dpdklab
2024-07-09 12:54 ` dpdklab
2024-07-09 12:57 ` dpdklab
2024-07-09 12:58 ` dpdklab
2024-07-09 13:05 ` dpdklab
2024-07-09 13:09 ` dpdklab
2024-07-09 13:12 ` dpdklab
2024-07-09 13:13 ` dpdklab
2024-07-09 13:15 ` dpdklab
2024-07-09 13:20 ` dpdklab
2024-07-09 13:21 ` dpdklab
2024-07-09 13:29 ` dpdklab
2024-07-09 13:35 ` dpdklab
2024-07-09 13:42 ` dpdklab
2024-07-09 13:42 ` dpdklab
2024-07-09 13:45 ` dpdklab
2024-07-09 13:45 ` dpdklab
2024-07-09 13:55 ` dpdklab
2024-07-09 13:58 ` dpdklab
2024-07-09 14:03 ` dpdklab
2024-07-09 14:07 ` dpdklab
2024-07-09 14:09 ` dpdklab
2024-07-09 14:10 ` dpdklab
2024-07-09 14:14 ` dpdklab
2024-07-09 14:41 ` |SUCCESS| " dpdklab
2024-07-09 15:00 ` dpdklab
2024-07-09 21:36 ` dpdklab
2024-07-09 23:07 ` dpdklab
2024-07-13 17:27 ` dpdklab
2024-07-14  9:29 ` dpdklab
2024-07-14 16:07 ` dpdklab
2024-07-15  6:05 ` dpdklab
2024-07-15  6:43 ` 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=668cc75d.050a0220.77b9d.2e02SMTPIN_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).