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| pw143716-143718 [PATCH] [v1,3/3] crypto/ipsec_mb: add SM4
Date: Fri, 06 Sep 2024 09:22:02 -0700 (PDT)	[thread overview]
Message-ID: <66db2c2a.c80a0220.37365c.f898SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906123939.2508919-3-brian.dooley@intel.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143718

_Functional Testing PASS_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Friday, September 06 2024 12:39:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

143716-143718 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#178964

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| scatter                     |  PASS  |
+-----------------------------+--------+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-06 16:22 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906123939.2508919-3-brian.dooley@intel.com>
2024-09-06 12:21 ` |SUCCESS| pw143716-143718 [PATCH v1 3/3] crypto/ipsec_mb: add SM4 algorithm support qemudev
2024-09-06 12:25 ` qemudev
2024-09-06 12:40 ` |SUCCESS| pw143718 " checkpatch
2024-09-06 13:44 ` 0-day Robot
2024-09-06 15:28 ` |PENDING| pw143716-143718 [PATCH] [v1,3/3] crypto/ipsec_mb: add SM4 dpdklab
2024-09-06 15:32 ` dpdklab
2024-09-06 15:32 ` |SUCCESS| " dpdklab
2024-09-06 15:33 ` dpdklab
2024-09-06 15:33 ` dpdklab
2024-09-06 15:34 ` dpdklab
2024-09-06 15:34 ` dpdklab
2024-09-06 16:16 ` |PENDING| " dpdklab
2024-09-06 16:16 ` dpdklab
2024-09-06 16:22 ` |SUCCESS| " dpdklab
2024-09-06 16:22 ` dpdklab [this message]
2024-09-06 16:22 ` dpdklab
2024-09-06 16:28 ` dpdklab
2024-09-06 16:30 ` dpdklab
2024-09-06 16:42 ` dpdklab
2024-09-06 18:06 ` dpdklab
2024-09-06 18:52 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:22 ` dpdklab
2024-09-06 21:24 ` dpdklab
2024-09-06 21:26 ` dpdklab
2024-09-06 21:27 ` dpdklab
2024-09-06 21:30 ` dpdklab
2024-09-06 21:32 ` dpdklab
2024-09-06 21:32 ` dpdklab
2024-09-06 21:35 ` dpdklab
2024-09-06 21:35 ` dpdklab
2024-09-06 21:48 ` dpdklab
2024-09-06 21:48 ` dpdklab
2024-09-06 21:52 ` dpdklab
2024-09-07  1:10 ` dpdklab
2024-09-07  1:14 ` dpdklab
2024-09-07  1:18 ` dpdklab
2024-09-07  1:22 ` dpdklab
2024-09-07  1:41 ` dpdklab
2024-09-07  1:49 ` dpdklab
2024-09-07  1:52 ` dpdklab
2024-09-07  1:57 ` dpdklab
2024-09-07  2:01 ` dpdklab
2024-09-07  2:20 ` dpdklab
2024-09-07  4:57 ` dpdklab
2024-09-07  6:31 ` dpdklab
2024-09-07  6:46 ` |PENDING| " dpdklab
2024-09-07  7:15 ` dpdklab
2024-09-07  8:28 ` |SUCCESS| " dpdklab
2024-09-07  8:29 ` dpdklab
2024-09-07  8:30 ` dpdklab
2024-09-07  9:05 ` dpdklab
2024-09-07  9:21 ` dpdklab
2024-09-08  2:12 ` dpdklab
2024-09-08  2:40 ` dpdklab
2024-09-17  8:28 ` dpdklab
2024-09-17  8:49 ` dpdklab
2024-09-17  9:08 ` dpdklab
2024-09-17  9:20 ` 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=66db2c2a.c80a0220.37365c.f898SMTPIN_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).