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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 7b20d58e710cd9d5e909a50c006fbc11577eb7bd
Date: Wed,  8 Mar 2023 10:33:21 +0000 (UTC)	[thread overview]
Message-ID: <20230308103321.4DDAA6011F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

_Testing PASS_

Branch: tags/v21.11

7b20d58e710cd9d5e909a50c006fbc11577eb7bd --> 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/23708/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-08 10:33 UTC|newest]

Thread overview: 264+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 10:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-20  4:08 dpdklab
2023-03-20  4:07 dpdklab
2023-03-20  4:04 dpdklab
2023-03-20  3:58 dpdklab
2023-03-20  3:56 dpdklab
2023-03-20  3:50 dpdklab
2023-03-20  3:43 dpdklab
2023-03-20  3:42 dpdklab
2023-03-20  3:37 dpdklab
2023-03-20  3:37 dpdklab
2023-03-20  3:28 dpdklab
2023-03-20  3:27 dpdklab
2023-03-19 15:59 dpdklab
2023-03-19  8:50 dpdklab
2023-03-18  7:27 dpdklab
2023-03-17 14:48 dpdklab
2023-03-17 10:54 dpdklab
2023-03-17  9:15 dpdklab
2023-03-17  9:07 dpdklab
2023-03-17  8:54 dpdklab
2023-03-17  8:13 dpdklab
2023-03-17  7:11 dpdklab
2023-03-17  7:11 dpdklab
2023-03-17  7:11 dpdklab
2023-03-17  7:06 dpdklab
2023-03-17  7:06 dpdklab
2023-03-17  7:02 dpdklab
2023-03-17  7:00 dpdklab
2023-03-17  7:00 dpdklab
2023-03-17  6:52 dpdklab
2023-03-17  6:51 dpdklab
2023-03-17  6:49 dpdklab
2023-03-17  6:48 dpdklab
2023-03-17  6:47 dpdklab
2023-03-17  6:39 dpdklab
2023-03-17  6:39 dpdklab
2023-03-17  6:19 dpdklab
2023-03-17  6:12 dpdklab
2023-03-17  6:06 dpdklab
2023-03-17  5:26 dpdklab
2023-03-17  5:15 dpdklab
2023-03-17  5:06 dpdklab
2023-03-17  5:06 dpdklab
2023-03-17  5:00 dpdklab
2023-03-17  4:54 dpdklab
2023-03-16  9:12 dpdklab
2023-03-16  9:06 dpdklab
2023-03-16  8:03 dpdklab
2023-03-16  5:34 dpdklab
2023-03-16  5:27 dpdklab
2023-03-16  5:25 dpdklab
2023-03-16  5:20 dpdklab
2023-03-16  5:19 dpdklab
2023-03-16  5:18 dpdklab
2023-03-16  5:14 dpdklab
2023-03-16  5:12 dpdklab
2023-03-16  5:08 dpdklab
2023-03-16  5:04 dpdklab
2023-03-16  5:02 dpdklab
2023-03-16  4:57 dpdklab
2023-03-16  4:55 dpdklab
2023-03-16  2:34 dpdklab
2023-03-15  8:46 dpdklab
2023-03-15  8:17 dpdklab
2023-03-15  6:24 dpdklab
2023-03-15  6:10 dpdklab
2023-03-15  6:10 dpdklab
2023-03-15  6:06 dpdklab
2023-03-15  6:00 dpdklab
2023-03-15  5:58 dpdklab
2023-03-15  5:57 dpdklab
2023-03-15  5:50 dpdklab
2023-03-15  5:47 dpdklab
2023-03-15  5:46 dpdklab
2023-03-15  5:45 dpdklab
2023-03-15  5:37 dpdklab
2023-03-15  5:33 dpdklab
2023-03-15  5:31 dpdklab
2023-03-15  5:26 dpdklab
2023-03-15  5:25 dpdklab
2023-03-15  5:22 dpdklab
2023-03-15  5:18 dpdklab
2023-03-15  5:13 dpdklab
2023-03-15  5:13 dpdklab
2023-03-15  5:11 dpdklab
2023-03-15  5:08 dpdklab
2023-03-15  5:04 dpdklab
2023-03-15  5:01 dpdklab
2023-03-15  4:57 dpdklab
2023-03-15  4:55 dpdklab
2023-03-15  4:51 dpdklab
2023-03-14 16:47 dpdklab
2023-03-14 15:25 dpdklab
2023-03-14  6:01 dpdklab
2023-03-14  5:52 dpdklab
2023-03-14  5:42 dpdklab
2023-03-14  5:39 dpdklab
2023-03-14  5:39 dpdklab
2023-03-14  5:33 dpdklab
2023-03-14  5:30 dpdklab
2023-03-14  5:29 dpdklab
2023-03-14  5:27 dpdklab
2023-03-14  5:23 dpdklab
2023-03-14  5:20 dpdklab
2023-03-14  5:12 dpdklab
2023-03-14  5:12 dpdklab
2023-03-14  5:09 dpdklab
2023-03-11 17:46 dpdklab
2023-03-11 12:51 dpdklab
2023-03-11 12:51 dpdklab
2023-03-11 12:44 dpdklab
2023-03-11 12:43 dpdklab
2023-03-11 12:39 dpdklab
2023-03-11 12:30 dpdklab
2023-03-11 12:26 dpdklab
2023-03-11 12:21 dpdklab
2023-03-11 12:20 dpdklab
2023-03-11 12:17 dpdklab
2023-03-11 12:14 dpdklab
2023-03-11 12:13 dpdklab
2023-03-11 12:00 dpdklab
2023-03-11  0:49 dpdklab
2023-03-11  0:40 dpdklab
2023-03-10  9:39 dpdklab
2023-03-10  9:18 dpdklab
2023-03-10  8:49 dpdklab
2023-03-10  8:36 dpdklab
2023-03-10  7:44 dpdklab
2023-03-10  7:39 dpdklab
2023-03-10  7:37 dpdklab
2023-03-10  7:26 dpdklab
2023-03-10  7:20 dpdklab
2023-03-10  7:20 dpdklab
2023-03-10  7:13 dpdklab
2023-03-10  6:54 dpdklab
2023-03-10  6:43 dpdklab
2023-03-10  6:08 dpdklab
2023-03-09  9:34 dpdklab
2023-03-09  7:19 dpdklab
2023-03-09  7:19 dpdklab
2023-03-09  7:18 dpdklab
2023-03-09  7:18 dpdklab
2023-03-09  7:15 dpdklab
2023-03-09  7:14 dpdklab
2023-03-09  7:13 dpdklab
2023-03-09  7:13 dpdklab
2023-03-09  7:12 dpdklab
2023-03-09  7:09 dpdklab
2023-03-09  7:07 dpdklab
2023-03-09  7:05 dpdklab
2023-03-09  7:00 dpdklab
2023-03-09  6:53 dpdklab
2023-03-09  6:52 dpdklab
2023-03-09  6:48 dpdklab
2023-03-09  6:21 dpdklab
2023-03-09  6:17 dpdklab
2023-03-09  6:17 dpdklab
2023-03-09  6:11 dpdklab
2023-03-09  6:11 dpdklab
2023-03-09  6:06 dpdklab
2023-03-09  6:06 dpdklab
2023-03-09  6:04 dpdklab
2023-03-09  6:03 dpdklab
2023-03-09  6:01 dpdklab
2023-03-09  6:01 dpdklab
2023-03-09  5:55 dpdklab
2023-03-09  5:52 dpdklab
2023-03-08 13:37 dpdklab
2023-03-08  7:44 dpdklab
2023-03-08  7:32 dpdklab
2023-03-08  7:12 dpdklab
2023-03-08  7:04 dpdklab
2023-03-08  6:34 dpdklab
2023-03-08  6:21 dpdklab
2023-03-08  6:16 dpdklab
2023-03-08  6:14 dpdklab
2023-03-08  6:10 dpdklab
2023-03-08  6:08 dpdklab
2023-03-08  6:06 dpdklab
2023-03-08  6:04 dpdklab
2023-03-08  6:02 dpdklab
2023-03-08  6:02 dpdklab
2023-03-08  5:58 dpdklab
2023-03-08  5:55 dpdklab
2023-03-07 14:27 dpdklab
2023-03-07 12:43 dpdklab
2023-03-07 11:45 dpdklab
2023-03-07 11:15 dpdklab
2023-03-07 11:15 dpdklab
2023-03-07 11:13 dpdklab
2023-03-07 11:11 dpdklab
2023-03-07 11:08 dpdklab
2023-03-07 11:04 dpdklab
2023-03-07 11:02 dpdklab
2023-03-07 10:59 dpdklab
2023-03-07 10:57 dpdklab
2023-03-07 10:54 dpdklab
2023-03-07 10:49 dpdklab
2023-03-07 10:37 dpdklab
2023-03-07 10:35 dpdklab
2023-03-07  9:44 dpdklab
2023-03-07  7:39 dpdklab
2023-03-07  7:24 dpdklab
2023-03-07  7:23 dpdklab
2023-03-07  7:21 dpdklab
2023-03-07  7:19 dpdklab
2023-03-07  7:13 dpdklab
2023-03-07  7:07 dpdklab
2023-03-07  7:07 dpdklab
2023-03-07  7:07 dpdklab
2023-03-07  7:04 dpdklab
2023-03-07  7:03 dpdklab
2023-03-07  7:01 dpdklab
2023-03-07  6:59 dpdklab
2023-03-07  6:48 dpdklab
2023-03-07  6:47 dpdklab
2023-03-07  6:32 dpdklab
2023-03-07  6:28 dpdklab
2023-03-07  6:20 dpdklab
2023-03-07  6:18 dpdklab
2023-03-07  6:13 dpdklab
2023-03-07  6:12 dpdklab
2023-03-07  6:08 dpdklab
2023-03-07  6:08 dpdklab
2023-03-07  6:07 dpdklab
2023-03-07  6:04 dpdklab
2023-03-07  6:01 dpdklab
2023-03-07  5:57 dpdklab
2023-03-07  4:53 dpdklab
2023-03-07  4:19 dpdklab
2023-03-07  4:18 dpdklab
2023-03-07  4:17 dpdklab
2023-03-07  4:12 dpdklab
2023-03-07  4:06 dpdklab
2023-03-07  4:06 dpdklab
2023-03-07  4:04 dpdklab
2023-03-07  4:03 dpdklab
2023-03-07  4:01 dpdklab
2023-03-07  3:59 dpdklab
2023-03-07  3:51 dpdklab
2023-03-01  0:27 dpdklab
2023-02-28 23:32 dpdklab
2023-02-28 23:27 dpdklab
2023-02-28 23:12 dpdklab
2023-02-28 23:10 dpdklab
2023-02-28 23:09 dpdklab
2023-02-28 23:06 dpdklab
2023-02-28 23:04 dpdklab
2023-02-28 22:59 dpdklab
2023-02-28 22:57 dpdklab
2023-02-28 22:56 dpdklab
2023-02-28 22:55 dpdklab
2023-02-28 22:42 dpdklab
2023-02-28 19:03 dpdklab
2023-02-28 19:01 dpdklab
2023-02-28 19:00 dpdklab
2023-02-28 18:54 dpdklab
2023-02-28 18:49 dpdklab
2023-02-28 18:48 dpdklab
2023-02-28 18:47 dpdklab
2023-02-28 18:45 dpdklab
2023-02-28 18:43 dpdklab
2023-02-28 18:37 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=20230308103321.4DDAA6011F@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).