automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Mingjin Ye <mingjinx.ye@intel.com>, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| pw132581 [PATCH] [v3] net/iavf: support no data path polli
Date: Thu, 12 Oct 2023 19:19:33 -0700 (PDT)	[thread overview]
Message-ID: <6528a935.0d0a0220.430af.57d3SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Friday, October 13 2023 01:27:37 
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: master
  CommitID:7c50ea8b57e25fe0c1ca01f87685e8e77e7ffadf

132581 --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| CentOS Stream 9 | PASS           |
+-----------------+----------------+
| Fedora 37       | PASS           |
+-----------------+----------------+
| Debian Buster   | PASS           |
+-----------------+----------------+
| Debian Bullseye | PASS           |
+-----------------+----------------+


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

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-13  2:19 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  2:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-13  3:57 dpdklab
2023-10-13  3:53 dpdklab
2023-10-13  3:50 dpdklab
2023-10-13  3:28 dpdklab
2023-10-13  2:52 dpdklab
2023-10-13  2:49 dpdklab
2023-10-13  2:47 dpdklab
2023-10-13  2:47 dpdklab
2023-10-13  2:46 dpdklab
2023-10-13  2:44 dpdklab
2023-10-13  2:43 dpdklab
2023-10-13  2:43 dpdklab
2023-10-13  2:43 dpdklab
2023-10-13  2:43 dpdklab
2023-10-13  2:39 dpdklab
2023-10-13  2:38 dpdklab
2023-10-13  2:37 dpdklab
2023-10-13  2:37 dpdklab
2023-10-13  2:36 dpdklab
2023-10-13  2:36 dpdklab
2023-10-13  2:19 dpdklab
2023-10-13  2:19 dpdklab
2023-10-13  2:19 dpdklab
2023-10-13  2:19 dpdklab
2023-10-13  2:19 dpdklab
2023-10-13  2:19 dpdklab
2023-10-13  2:18 dpdklab
2023-10-13  2:17 dpdklab
2023-10-13  2:17 dpdklab
2023-10-13  2:16 dpdklab
2023-10-13  2:15 dpdklab
2023-10-13  2:15 dpdklab
2023-10-13  2:15 dpdklab
2023-10-13  2:15 dpdklab
2023-10-13  2:14 dpdklab
2023-10-13  2:14 dpdklab
2023-10-13  2:14 dpdklab
2023-10-13  2:13 dpdklab
2023-10-13  2:13 dpdklab
2023-10-13  2:12 dpdklab
2023-10-13  2:12 dpdklab
2023-10-13  2:06 dpdklab
2023-10-13  2:06 dpdklab
2023-10-13  2:06 dpdklab
2023-10-13  2:06 dpdklab
2023-10-13  2:06 dpdklab
2023-10-13  2:06 dpdklab
2023-10-13  2:06 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=6528a935.0d0a0220.430af.57d3SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=mingjinx.ye@intel.com \
    --cc=qi.z.zhang@intel.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).