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| pw126218 [PATCH] usertools: enhance CPU layout
Date: Tue, 18 Apr 2023 19:44:26 +0000 (UTC)	[thread overview]
Message-ID: <20230418194426.B234560095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126218

_Testing PASS_

Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Tuesday, April 18 2023 05:25:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd

126218 --> testing pass

Test environment and result as below:

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


Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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/26026/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-18 19:44 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 19:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-18 19:44 dpdklab
2023-04-18 18:35 dpdklab
2023-04-18 18:34 dpdklab
2023-04-18 13:40 dpdklab
2023-04-18 13:29 dpdklab
2023-04-18 12:54 dpdklab
2023-04-18 12:16 dpdklab
2023-04-18  9:43 dpdklab
2023-04-18  9:26 dpdklab
2023-04-18  9:23 dpdklab
2023-04-18  9:21 dpdklab
2023-04-18  9:16 dpdklab
2023-04-18  9:11 dpdklab
2023-04-18  9:08 dpdklab
2023-04-18  9:03 dpdklab
2023-04-18  9:02 dpdklab
2023-04-18  9:01 dpdklab
2023-04-18  9:00 dpdklab
2023-04-18  8:58 dpdklab
2023-04-18  8:56 dpdklab
2023-04-18  8:50 dpdklab
2023-04-18  8:46 dpdklab
2023-04-18  8:45 dpdklab
2023-04-18  8:35 dpdklab
2023-04-18  8:31 dpdklab
2023-04-18  8:27 dpdklab
2023-04-18  8:24 dpdklab
2023-04-18  8:24 dpdklab
2023-04-18  8:20 dpdklab
2023-04-18  8:20 dpdklab
2023-04-18  8:19 dpdklab
2023-04-18  8:18 dpdklab
2023-04-18  8:17 dpdklab
2023-04-18  8:13 dpdklab
2023-04-18  8:11 dpdklab
2023-04-18  8:08 dpdklab
2023-04-18  8:08 dpdklab
2023-04-18  8:07 dpdklab
2023-04-18  8:05 dpdklab
2023-04-18  8:04 dpdklab
2023-04-18  8:00 dpdklab
2023-04-18  8:00 dpdklab
2023-04-18  7:53 dpdklab
2023-04-18  7:41 dpdklab
2023-04-18  7:29 dpdklab
2023-04-18  7:20 dpdklab
2023-04-18  7:18 dpdklab
2023-04-18  7:16 dpdklab
2023-04-18  7:11 dpdklab
2023-04-18  7:06 dpdklab
2023-04-18  7:04 dpdklab
2023-04-18  6:58 dpdklab
2023-04-18  6:56 dpdklab
2023-04-18  6:56 dpdklab
2023-04-18  6:55 dpdklab
2023-04-18  6:50 dpdklab
     [not found] <1681795541-68384-1-git-send-email-wenzhuo.lu@intel.com>
2023-04-18  5:49 ` qemudev
2023-04-18  5:53 ` qemudev
2023-04-18  6:59 ` 0-day Robot

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=20230418194426.B234560095@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).