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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw132370 [PATCH] [v4] app/testpmd: enable cli for programm
Date: Sat, 07 Oct 2023 03:54:49 -0700 (PDT)	[thread overview]
Message-ID: <652138f9.170a0220.165bb.02f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Saturday, October 07 2023 10:47:30 
DPDK git baseline: Repo:dpdk-next-net
  Branch: master
  CommitID:40435075a790fac6e5d5ad7a967950f5e56e45c8

132370 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+


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

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-07 10:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 10:54 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-07 12:09 dpdklab
2023-10-07 12:07 dpdklab
2023-10-07 12:02 dpdklab
2023-10-07 11:53 dpdklab
2023-10-07 11:53 dpdklab
2023-10-07 11:49 dpdklab
2023-10-07 11:42 dpdklab
2023-10-07 11:40 dpdklab
2023-10-07 11:40 dpdklab
2023-10-07 11:37 dpdklab
2023-10-07 11:37 dpdklab
2023-10-07 11:35 dpdklab
2023-10-07 11:33 dpdklab
2023-10-07 11:29 dpdklab
2023-10-07 11:27 dpdklab
2023-10-07 11:23 dpdklab
2023-10-07 11:16 dpdklab
2023-10-07 11:15 dpdklab
2023-10-07 11:15 dpdklab
2023-10-07 11:08 dpdklab
2023-10-07 11:07 dpdklab
2023-10-07 11:05 dpdklab
2023-10-07 11:01 dpdklab
2023-10-07 10:54 dpdklab
2023-10-07 10:52 dpdklab
2023-10-07 10:49 dpdklab
2023-10-07 10:48 dpdklab
2023-10-07 10:47 dpdklab
2023-10-07 10:41 dpdklab
2023-10-07 10:38 dpdklab
2023-10-07 10:38 dpdklab
2023-10-07 10:38 dpdklab
2023-10-07 10:38 dpdklab
2023-10-07 10:37 dpdklab
2023-10-07 10:37 dpdklab
2023-10-07 10:36 dpdklab
2023-10-07 10:36 dpdklab
2023-10-07 10:36 dpdklab
2023-10-07 10:33 dpdklab
2023-10-07 10:33 dpdklab
2023-10-07 10:32 dpdklab
2023-10-07 10:31 dpdklab
2023-10-07 10:31 dpdklab
2023-10-07 10:31 dpdklab
2023-10-07 10:31 dpdklab
2023-10-07 10:30 dpdklab
2023-10-07 10:30 dpdklab
2023-10-07 10:27 dpdklab
2023-10-07 10:26 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=652138f9.170a0220.165bb.02f4SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.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).