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| pw124605 [PATCH] [v2] net/idpf: refine Rx/Tx queue model info
Date: Wed, 1 Mar 2023 18:20:35 +0000 (UTC) [thread overview]
Message-ID: <20230301182035.3DBFF601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124605
_Functional Testing PASS_
Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Wednesday, March 01 2023 19:26:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124605 --> 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 Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 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: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25572/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-01 18:20 UTC|newest]
Thread overview: 121+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 18:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-02 11:58 dpdklab
2023-03-02 11:58 dpdklab
2023-03-02 11:54 dpdklab
2023-03-02 11:51 dpdklab
2023-03-02 11:48 dpdklab
2023-03-02 11:46 dpdklab
2023-03-02 11:43 dpdklab
2023-03-02 11:41 dpdklab
2023-03-02 11:38 dpdklab
2023-03-02 11:24 dpdklab
2023-03-02 11:23 dpdklab
2023-03-02 11:22 dpdklab
2023-03-02 11:20 dpdklab
2023-03-02 11:19 dpdklab
2023-03-02 11:15 dpdklab
2023-03-02 11:14 dpdklab
2023-03-02 11:12 dpdklab
2023-03-02 11:09 dpdklab
2023-03-02 11:08 dpdklab
2023-03-02 10:57 dpdklab
2023-03-02 10:54 dpdklab
2023-03-02 10:54 dpdklab
2023-03-02 10:52 dpdklab
2023-03-02 10:49 dpdklab
2023-03-02 10:35 dpdklab
2023-03-02 10:33 dpdklab
2023-03-02 10:31 dpdklab
2023-03-02 10:30 dpdklab
2023-03-02 10:30 dpdklab
2023-03-02 10:29 dpdklab
2023-03-02 10:24 dpdklab
2023-03-02 10:23 dpdklab
2023-03-02 10:15 dpdklab
2023-03-02 10:12 dpdklab
2023-03-02 10:10 dpdklab
2023-03-02 10:08 dpdklab
2023-03-02 10:05 dpdklab
2023-03-02 9:55 dpdklab
2023-03-02 9:53 dpdklab
2023-03-02 9:53 dpdklab
2023-03-02 9:48 dpdklab
2023-03-02 9:45 dpdklab
2023-03-02 9:44 dpdklab
2023-03-02 9:39 dpdklab
2023-03-02 9:39 dpdklab
2023-03-02 9:37 dpdklab
2023-03-02 9:35 dpdklab
2023-03-02 9:23 dpdklab
2023-03-02 9:16 dpdklab
2023-03-02 9:10 dpdklab
2023-03-02 9:09 dpdklab
2023-03-02 9:07 dpdklab
2023-03-02 9:05 dpdklab
2023-03-02 9:04 dpdklab
2023-03-02 9:03 dpdklab
2023-03-02 9:03 dpdklab
2023-03-02 9:02 dpdklab
2023-03-02 8:59 dpdklab
2023-03-02 8:50 dpdklab
2023-03-02 8:42 dpdklab
2023-03-02 8:41 dpdklab
2023-03-02 8:38 dpdklab
2023-03-02 8:36 dpdklab
2023-03-02 8:28 dpdklab
2023-03-02 8:27 dpdklab
2023-03-02 8:25 dpdklab
2023-03-02 8:23 dpdklab
2023-03-02 8:18 dpdklab
2023-03-02 8:16 dpdklab
2023-03-01 21:08 dpdklab
2023-03-01 20:10 dpdklab
2023-03-01 20:09 dpdklab
2023-03-01 20:06 dpdklab
2023-03-01 19:31 dpdklab
2023-03-01 19:28 dpdklab
2023-03-01 19:11 dpdklab
2023-03-01 19:09 dpdklab
2023-03-01 19:08 dpdklab
2023-03-01 19:04 dpdklab
2023-03-01 18:55 dpdklab
2023-03-01 18:54 dpdklab
2023-03-01 18:40 dpdklab
2023-03-01 18:39 dpdklab
2023-03-01 18:39 dpdklab
2023-03-01 18:30 dpdklab
2023-03-01 18:30 dpdklab
2023-03-01 18:29 dpdklab
2023-03-01 18:29 dpdklab
2023-03-01 18:28 dpdklab
2023-03-01 18:27 dpdklab
2023-03-01 18:25 dpdklab
2023-03-01 18:23 dpdklab
2023-03-01 18:20 dpdklab
2023-03-01 18:20 dpdklab
2023-03-01 18:19 dpdklab
2023-03-01 18:16 dpdklab
2023-03-01 18:13 dpdklab
2023-03-01 18:12 dpdklab
2023-03-01 18:10 dpdklab
2023-03-01 18:10 dpdklab
2023-03-01 18:09 dpdklab
2023-03-01 18:06 dpdklab
2023-03-01 18:05 dpdklab
2023-03-01 18:03 dpdklab
2023-03-01 18:02 dpdklab
2023-03-01 18:01 dpdklab
2023-03-01 18:00 dpdklab
2023-03-01 17:56 dpdklab
2023-03-01 17:54 dpdklab
2023-03-01 17:46 dpdklab
2023-03-01 17:44 dpdklab
2023-03-01 17:39 dpdklab
2023-03-01 17:39 dpdklab
2023-03-01 17:39 dpdklab
2023-03-01 17:35 dpdklab
2023-03-01 17:33 dpdklab
[not found] <20230301192659.601892-1-mingxia.liu@intel.com>
2023-03-01 11:02 ` |SUCCESS| pw124605 [PATCH v2] " qemudev
2023-03-01 11:05 ` qemudev
2023-03-01 11:13 ` checkpatch
2023-03-01 12: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=20230301182035.3DBFF601B1@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).