From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133732-133734 [PATCH] [v6,3/3] net/tap; rebuild and upda
Date: Wed, 01 Nov 2023 13:30:51 -0700 (PDT) [thread overview]
Message-ID: <6542b57b.630a0220.8b460.246cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133734
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, November 01 2023 18:02:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6
133732-133734 --> functional testing pass
Test environment and result as below:
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28184/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-01 20:30 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 20:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 11:32 dpdklab
2023-11-02 5:52 dpdklab
2023-11-02 0:43 dpdklab
2023-11-02 0:34 dpdklab
2023-11-02 0:27 dpdklab
2023-11-02 0:18 dpdklab
2023-11-02 0:18 dpdklab
2023-11-01 23:56 dpdklab
2023-11-01 23:56 dpdklab
2023-11-01 23:49 dpdklab
2023-11-01 23:47 dpdklab
2023-11-01 23:44 dpdklab
2023-11-01 23:31 dpdklab
2023-11-01 23:30 dpdklab
2023-11-01 23:25 dpdklab
2023-11-01 23:19 dpdklab
2023-11-01 23:18 dpdklab
2023-11-01 23:18 dpdklab
2023-11-01 23:18 dpdklab
2023-11-01 23:18 dpdklab
2023-11-01 23:14 dpdklab
2023-11-01 23:14 dpdklab
2023-11-01 23:13 dpdklab
2023-11-01 23:12 dpdklab
2023-11-01 23:12 dpdklab
2023-11-01 22:56 dpdklab
2023-11-01 22:56 dpdklab
2023-11-01 22:56 dpdklab
2023-11-01 22:55 dpdklab
2023-11-01 22:55 dpdklab
2023-11-01 22:55 dpdklab
2023-11-01 22:54 dpdklab
2023-11-01 22:54 dpdklab
2023-11-01 22:54 dpdklab
2023-11-01 22:53 dpdklab
2023-11-01 22:53 dpdklab
2023-11-01 22:50 dpdklab
2023-11-01 22:49 dpdklab
2023-11-01 22:48 dpdklab
2023-11-01 22:47 dpdklab
2023-11-01 22:47 dpdklab
2023-11-01 22:47 dpdklab
2023-11-01 22:46 dpdklab
2023-11-01 22:44 dpdklab
2023-11-01 21:54 dpdklab
2023-11-01 21:27 dpdklab
2023-11-01 21:25 dpdklab
2023-11-01 21:09 dpdklab
2023-11-01 21:05 dpdklab
2023-11-01 21:01 dpdklab
2023-11-01 20:29 dpdklab
2023-11-01 20:28 dpdklab
2023-11-01 20:23 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=6542b57b.630a0220.8b460.246cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).