automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Jie Hai <haijie1@huawei.com>
Subject: |SUCCESS| pw132080-132086 [PATCH] [v2,8/8] app/testpmd: fix primary
Date: Thu, 28 Sep 2023 10:48:12 -0700 (PDT)	[thread overview]
Message-ID: <6515bc5c.0d0a0220.c8c5e.8d95SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Thursday, September 28 2023 07:43:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c56185fc183fc0532d2f03aaf04bbf0989ea91a5

132080-132086 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian Buster       | 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

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-28 17:48 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 17:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-28 21:06 dpdklab
2023-09-28 18:36 dpdklab
2023-09-28 18:10 dpdklab
2023-09-28 18:08 dpdklab
2023-09-28 18:08 dpdklab
2023-09-28 18:03 dpdklab
2023-09-28 18:00 dpdklab
2023-09-28 17:54 dpdklab
2023-09-28 17:49 dpdklab
2023-09-28 17:45 dpdklab
2023-09-28 17:42 dpdklab
2023-09-28 17:42 dpdklab
2023-09-28 17:34 dpdklab
2023-09-28 16:38 dpdklab
2023-09-28 16:38 dpdklab
2023-09-28 16:28 dpdklab
2023-09-28 16:27 dpdklab
2023-09-28 16:26 dpdklab
2023-09-28 16:26 dpdklab
2023-09-28 16:25 dpdklab
2023-09-28 16:23 dpdklab
2023-09-28 16:23 dpdklab
2023-09-28 16:22 dpdklab
2023-09-28 16:22 dpdklab
2023-09-28 16:15 dpdklab
2023-09-28 16:15 dpdklab
2023-09-28 16:07 dpdklab
2023-09-28 15:59 dpdklab
2023-09-28 15:53 dpdklab
2023-09-28 15:53 dpdklab
2023-09-28 15:52 dpdklab
2023-09-28 15:51 dpdklab
2023-09-28 15:50 dpdklab
2023-09-28 15:49 dpdklab
2023-09-28 15:41 dpdklab
2023-09-28 15:40 dpdklab
2023-09-28 15:31 dpdklab
2023-09-28 15:18 dpdklab
2023-09-28 15:14 dpdklab
2023-09-28 15:13 dpdklab
2023-09-28 15:10 dpdklab
2023-09-28 15:09 dpdklab
2023-09-28 15:06 dpdklab
2023-09-28 14:58 dpdklab
2023-09-28 14:54 dpdklab
2023-09-28 14:50 dpdklab
2023-09-28 14:49 dpdklab
2023-09-28 14: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=6515bc5c.0d0a0220.c8c5e.8d95SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=haijie1@huawei.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).