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| pw141727-141732 [PATCH] [6/6] crypto/ccp: use a dynamic lo
Date: Tue, 25 Jun 2024 08:48:26 -0700 (PDT)	[thread overview]
Message-ID: <667ae6ca.050a0220.892cf.3171SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240625122414.1065829-7-david.marchand@redhat.com>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141732

_Functional Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, June 25 2024 12:24:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9ab7baa5c14b1ba928c09bda4734827d6d367d6b

141727-141732 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| cmdline         |  PASS  |
+-----------------+--------+
| coremask        |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| l2fwd           |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-25 15:48 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240625122414.1065829-7-david.marchand@redhat.com>
2024-06-25 12:04 ` |SUCCESS| pw141727-141732 [PATCH 6/6] crypto/ccp: use a dynamic logtype qemudev
2024-06-25 12:09 ` qemudev
2024-06-25 12:27 ` |SUCCESS| pw141732 " checkpatch
2024-06-25 13:25 ` 0-day Robot
2024-06-25 14:59 ` |SUCCESS| pw141727-141732 [PATCH] [6/6] crypto/ccp: use a dynamic lo dpdklab
2024-06-25 15:00 ` dpdklab
2024-06-25 15:00 ` dpdklab
2024-06-25 15:04 ` dpdklab
2024-06-25 15:06 ` dpdklab
2024-06-25 15:09 ` dpdklab
2024-06-25 15:09 ` dpdklab
2024-06-25 15:11 ` dpdklab
2024-06-25 15:11 ` dpdklab
2024-06-25 15:11 ` dpdklab
2024-06-25 15:12 ` dpdklab
2024-06-25 15:12 ` dpdklab
2024-06-25 15:32 ` dpdklab
2024-06-25 15:47 ` dpdklab
2024-06-25 15:48 ` dpdklab [this message]
2024-06-25 15:52 ` dpdklab
2024-06-25 15:54 ` dpdklab
2024-06-25 15:59 ` dpdklab
2024-06-25 16:04 ` dpdklab
2024-06-25 16:06 ` dpdklab
2024-06-25 16:07 ` dpdklab
2024-06-25 16:10 ` dpdklab
2024-06-25 16:12 ` dpdklab
2024-06-25 16:12 ` dpdklab
2024-06-25 16:13 ` dpdklab
2024-06-25 16:14 ` dpdklab
2024-06-25 16:15 ` dpdklab
2024-06-25 16:24 ` dpdklab
2024-06-25 16:25 ` dpdklab
2024-06-25 16:26 ` dpdklab
2024-06-25 16:26 ` dpdklab
2024-06-25 16:31 ` dpdklab
2024-06-25 16:32 ` dpdklab
2024-06-25 16:46 ` dpdklab
2024-06-25 16:48 ` dpdklab
2024-06-25 16:48 ` dpdklab
2024-06-25 16:48 ` dpdklab
2024-06-25 16:49 ` dpdklab
2024-06-25 16:50 ` dpdklab
2024-06-25 16:50 ` dpdklab
2024-06-25 16:50 ` dpdklab
2024-06-25 16:51 ` dpdklab
2024-06-25 16:51 ` dpdklab
2024-06-25 16:51 ` dpdklab
2024-06-25 16:52 ` dpdklab
2024-06-25 16:52 ` dpdklab
2024-06-25 16:53 ` dpdklab
2024-06-25 16:54 ` dpdklab
2024-06-25 16:54 ` dpdklab
2024-06-25 16:55 ` dpdklab
2024-06-25 16:55 ` dpdklab
2024-06-25 16:56 ` dpdklab
2024-06-25 16:57 ` dpdklab
2024-06-25 16:57 ` dpdklab
2024-06-25 16:57 ` dpdklab
2024-06-25 16:58 ` dpdklab
2024-06-25 16:58 ` dpdklab
2024-06-25 16:58 ` dpdklab
2024-06-25 16:58 ` dpdklab
2024-06-25 16:59 ` dpdklab
2024-06-25 16:59 ` dpdklab
2024-06-25 16:59 ` dpdklab
2024-06-25 16:59 ` dpdklab
2024-06-25 16:59 ` dpdklab
2024-06-25 16:59 ` dpdklab
2024-06-25 17:00 ` dpdklab
2024-06-25 17:00 ` dpdklab
2024-06-25 17:01 ` dpdklab
2024-06-25 17:01 ` dpdklab
2024-06-25 17:02 ` dpdklab
2024-06-25 17:02 ` dpdklab
2024-06-25 17:03 ` dpdklab
2024-06-25 17:04 ` dpdklab
2024-06-25 17:04 ` dpdklab
2024-06-25 17:05 ` dpdklab
2024-06-25 17:06 ` dpdklab
2024-06-25 17:06 ` dpdklab
2024-06-25 17:06 ` dpdklab
2024-06-25 17:07 ` dpdklab
2024-06-25 17:07 ` dpdklab
2024-06-25 17:07 ` dpdklab
2024-06-25 17:08 ` dpdklab
2024-06-25 17:08 ` dpdklab
2024-06-25 17:08 ` dpdklab
2024-06-25 17:09 ` dpdklab
2024-06-25 17:09 ` dpdklab
2024-06-25 17:09 ` dpdklab
2024-06-25 17:10 ` dpdklab
2024-06-25 17:10 ` dpdklab
2024-06-25 17:10 ` dpdklab
2024-06-25 17:10 ` dpdklab
2024-06-25 17:11 ` dpdklab
2024-06-25 17:11 ` dpdklab
2024-06-25 17:11 ` dpdklab
2024-06-25 17:11 ` dpdklab
2024-06-25 17:12 ` dpdklab
2024-06-25 17:12 ` dpdklab
2024-06-25 17:13 ` dpdklab
2024-06-25 17:15 ` dpdklab
2024-06-25 17:16 ` dpdklab
2024-06-25 17:16 ` dpdklab
2024-06-25 17:18 ` dpdklab
2024-06-25 17:19 ` dpdklab
2024-06-25 17:19 ` dpdklab
2024-06-25 17:24 ` dpdklab
2024-06-25 17:31 ` dpdklab
2024-06-25 17:53 ` dpdklab
2024-06-25 18:06 ` 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=667ae6ca.050a0220.892cf.3171SMTPIN_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).