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| pw133444-133467 [PATCH] [v4,24/24] vdpa/nfp: add device op
Date: Fri, 27 Oct 2023 02:43:32 -0700 (PDT) [thread overview]
Message-ID: <653b8644.050a0220.6be25.2e78SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133467
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, October 27 2023 03:00:01
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:7fd6c31f938a33e1837bab2b14c2861bdd224b93
133444-133467 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28104/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-27 9:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 9:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 16:31 dpdklab
2023-10-27 11:15 dpdklab
2023-10-27 11:09 dpdklab
2023-10-27 11:03 dpdklab
2023-10-27 11:01 dpdklab
2023-10-27 10:49 dpdklab
2023-10-27 10:46 dpdklab
2023-10-27 10:45 dpdklab
2023-10-27 10:45 dpdklab
2023-10-27 10:44 dpdklab
2023-10-27 10:43 dpdklab
2023-10-27 10:43 dpdklab
2023-10-27 10:42 dpdklab
2023-10-27 10:41 dpdklab
2023-10-27 10:40 dpdklab
2023-10-27 10:36 dpdklab
2023-10-27 10:27 dpdklab
2023-10-27 10:23 dpdklab
2023-10-27 10:22 dpdklab
2023-10-27 10:05 dpdklab
2023-10-27 10:04 dpdklab
2023-10-27 10:03 dpdklab
2023-10-27 10:02 dpdklab
2023-10-27 10:02 dpdklab
2023-10-27 10:02 dpdklab
2023-10-27 10:02 dpdklab
2023-10-27 10:02 dpdklab
2023-10-27 10:02 dpdklab
2023-10-27 10:01 dpdklab
2023-10-27 10:01 dpdklab
2023-10-27 10:01 dpdklab
2023-10-27 10:01 dpdklab
2023-10-27 10:00 dpdklab
2023-10-27 10:00 dpdklab
2023-10-27 10:00 dpdklab
2023-10-27 9:59 dpdklab
2023-10-27 9:58 dpdklab
2023-10-27 9:51 dpdklab
2023-10-27 9:50 dpdklab
2023-10-27 9:50 dpdklab
2023-10-27 9:50 dpdklab
2023-10-27 9:49 dpdklab
2023-10-27 9:48 dpdklab
2023-10-27 9:47 dpdklab
2023-10-27 9:46 dpdklab
2023-10-27 9:45 dpdklab
2023-10-27 9:45 dpdklab
2023-10-27 9:28 dpdklab
2023-10-27 9:25 dpdklab
2023-10-27 9:24 dpdklab
2023-10-27 9:24 dpdklab
2023-10-27 9:21 dpdklab
2023-10-27 9:20 dpdklab
2023-10-27 9:20 dpdklab
2023-10-27 9:19 dpdklab
2023-10-27 9:15 dpdklab
2023-10-27 9:14 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=653b8644.050a0220.6be25.2e78SMTPIN_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).