automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Rakesh Kudurumalla <rkudurumalla@marvell.com>,
	dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132016-132017 [PATCH] [v5,2/2] node: add UDP v4 support
Date: Wed, 27 Sep 2023 08:57:00 -0700 (PDT)	[thread overview]
Message-ID: <651450cc.0d0a0220.5cd25.dccfSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132017

_Testing PASS_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Wednesday, September 27 2023 12:41:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d58c97481a136ad5342c9d8717b22bdaa5eccd43

132016-132017 --> testing pass

Test environment and result as below:

+-----------------+------------------------------+
|   Environment   | cryptodev_sw_snow3g_autotest |
+=================+==============================+
| Debian 11 (arm) | PASS                         |
+-----------------+------------------------------+


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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-27 15:57 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 15:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-27 20:58 dpdklab
2023-09-27 17:13 dpdklab
2023-09-27 16:47 dpdklab
2023-09-27 16:46 dpdklab
2023-09-27 16:45 dpdklab
2023-09-27 16:44 dpdklab
2023-09-27 16:32 dpdklab
2023-09-27 16:31 dpdklab
2023-09-27 16:31 dpdklab
2023-09-27 16:30 dpdklab
2023-09-27 16:29 dpdklab
2023-09-27 16:28 dpdklab
2023-09-27 16:28 dpdklab
2023-09-27 16:27 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:26 dpdklab
2023-09-27 16:25 dpdklab
2023-09-27 16:25 dpdklab
2023-09-27 16:12 dpdklab
2023-09-27 16:06 dpdklab
2023-09-27 16:06 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:05 dpdklab
2023-09-27 16:00 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:58 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:57 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:56 dpdklab
2023-09-27 15:55 dpdklab
2023-09-27 15:55 dpdklab
2023-09-27 15:55 dpdklab
2023-09-27 15:54 dpdklab
2023-09-27 15:54 dpdklab
2023-09-27 15:53 dpdklab
2023-09-27 15:53 dpdklab
     [not found] <20230927124100.4108588-2-rkudurumalla@marvell.com>
2023-09-27 12:27 ` |SUCCESS| pw132016-132017 [PATCH v5 2/2] " qemudev
2023-09-27 12:32 ` qemudev

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=651450cc.0d0a0220.5cd25.dccfSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=rkudurumalla@marvell.com \
    --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).