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| pw132029-132032 [PATCH] [v3,4/4] mldev: update release not
Date: Wed, 27 Sep 2023 12:19:21 -0700 (PDT)	[thread overview]
Message-ID: <65148039.250a0220.3f369.5757SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132032

_Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, September 27 2023 18:11:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d58c97481a136ad5342c9d8717b22bdaa5eccd43

132029-132032 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


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

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

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 19:19 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 19:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-27 23:09 dpdklab
2023-09-27 20:33 dpdklab
2023-09-27 20:14 dpdklab
2023-09-27 20:11 dpdklab
2023-09-27 20:10 dpdklab
2023-09-27 20:08 dpdklab
2023-09-27 20:06 dpdklab
2023-09-27 20:03 dpdklab
2023-09-27 20:00 dpdklab
2023-09-27 19:51 dpdklab
2023-09-27 19:48 dpdklab
2023-09-27 19:47 dpdklab
2023-09-27 19:44 dpdklab
2023-09-27 19:43 dpdklab
2023-09-27 19:28 dpdklab
2023-09-27 19:26 dpdklab
2023-09-27 19:25 dpdklab
2023-09-27 19:25 dpdklab
2023-09-27 19:24 dpdklab
2023-09-27 19:23 dpdklab
2023-09-27 19:23 dpdklab
2023-09-27 19:23 dpdklab
2023-09-27 19:23 dpdklab
2023-09-27 19:22 dpdklab
2023-09-27 19:22 dpdklab
2023-09-27 19:22 dpdklab
2023-09-27 19:22 dpdklab
2023-09-27 19:22 dpdklab
2023-09-27 19:21 dpdklab
2023-09-27 19:21 dpdklab
2023-09-27 19:21 dpdklab
2023-09-27 19:20 dpdklab
2023-09-27 19:20 dpdklab
2023-09-27 19:20 dpdklab
2023-09-27 19:20 dpdklab
2023-09-27 19:20 dpdklab
2023-09-27 19:19 dpdklab
2023-09-27 19:19 dpdklab
2023-09-27 19:18 dpdklab
2023-09-27 19:18 dpdklab
2023-09-27 19:17 dpdklab
2023-09-27 19:17 dpdklab
2023-09-27 19:17 dpdklab
2023-09-27 19:16 dpdklab
2023-09-27 19:16 dpdklab
2023-09-27 19:16 dpdklab
2023-09-27 19:15 dpdklab
2023-09-27 19:13 dpdklab
2023-09-27 19:12 dpdklab
2023-09-27 19:11 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=65148039.250a0220.3f369.5757SMTPIN_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).