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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| [GIT MASTER] ce5440e0350df101443aa4d0e96bea0a06ef9364
Date: Mon, 20 Mar 2023 22:42:47 +0000 (UTC)	[thread overview]
Message-ID: <20230320224247.4E39460214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

_Testing PASS_

Branch: dpdk

ce5440e0350df101443aa4d0e96bea0a06ef9364 --> 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/tarballs/23930/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-20 22:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 22:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-21 22:50 dpdklab
2023-03-20  0:03 dpdklab
2023-03-19 12:49 dpdklab
2023-03-17 18:53 dpdklab
2023-03-17 17:47 dpdklab
2023-03-17 17:36 dpdklab
2023-03-17 17:36 dpdklab
2023-03-17 17:34 dpdklab
2023-03-17 17:27 dpdklab
2023-03-17 17:24 dpdklab
2023-03-17 17:19 dpdklab
2023-03-17 17:02 dpdklab
2023-03-17 17:00 dpdklab
2023-03-17 16:55 dpdklab
2023-03-17 16:52 dpdklab
2023-03-17 16:49 dpdklab
2023-03-17 16:45 dpdklab
2023-03-17 16:41 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=20230320224247.4E39460214@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).