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| pw124604 [PATCH] net/idpf: optimize Tx/Rx qeue mode code
Date: Wed,  1 Mar 2023 08:54:32 +0000 (UTC)	[thread overview]
Message-ID: <20230301085432.46991601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124604

_Functional Testing PASS_

Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Wednesday, March 01 2023 16:16:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7710b5d15a014872a3aaf646668dafa928ca8473

124604 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-01  8:54 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  8:54 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-02  6:05 dpdklab
2023-03-02  6:04 dpdklab
2023-03-02  6:00 dpdklab
2023-03-02  5:57 dpdklab
2023-03-02  5:56 dpdklab
2023-03-02  5:54 dpdklab
2023-03-02  5:53 dpdklab
2023-03-02  5:51 dpdklab
2023-03-02  5:50 dpdklab
2023-03-02  5:49 dpdklab
2023-03-02  5:46 dpdklab
2023-03-02  5:44 dpdklab
2023-03-02  5:42 dpdklab
2023-03-02  5:33 dpdklab
2023-03-02  5:28 dpdklab
2023-03-02  5:28 dpdklab
2023-03-02  5:23 dpdklab
2023-03-02  5:19 dpdklab
2023-03-02  5:16 dpdklab
2023-03-02  5:16 dpdklab
2023-03-02  5:14 dpdklab
2023-03-02  5:12 dpdklab
2023-03-02  5:06 dpdklab
2023-03-02  5:01 dpdklab
2023-03-02  4:57 dpdklab
2023-03-02  4:56 dpdklab
2023-03-02  4:55 dpdklab
2023-03-01 16:21 dpdklab
2023-03-01 15:31 dpdklab
2023-03-01 15:30 dpdklab
2023-03-01 14:23 dpdklab
2023-03-01 12:49 dpdklab
2023-03-01 12:37 dpdklab
2023-03-01 12:17 dpdklab
2023-03-01 12:04 dpdklab
2023-03-01 10:56 dpdklab
2023-03-01 10:44 dpdklab
2023-03-01 10:28 dpdklab
     [not found] <20230301161605.436754-1-mingxia.liu@intel.com>
2023-03-01  7:52 ` qemudev
2023-03-01  7:55 ` qemudev
2023-03-01  8:01 ` checkpatch
2023-03-01 10:19 ` 0-day Robot
2023-03-01 10:12 dpdklab
2023-03-01  9:50 dpdklab
2023-03-01  9:31 dpdklab
2023-03-01  9:28 dpdklab
2023-03-01  9:25 dpdklab
2023-03-01  9:24 dpdklab
2023-03-01  9:22 dpdklab
2023-03-01  9:21 dpdklab
2023-03-01  9:19 dpdklab
2023-03-01  9:19 dpdklab
2023-03-01  9:12 dpdklab
2023-03-01  8:57 dpdklab
2023-03-01  8:51 dpdklab
2023-03-01  8:50 dpdklab
2023-03-01  8:46 dpdklab
2023-03-01  8:45 dpdklab
2023-03-01  8:45 dpdklab
2023-03-01  8:39 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=20230301085432.46991601B1@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).