From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139035-139064 [PATCH] [v3,30/30] examples: replace use o
Date: Tue, 02 Apr 2024 22:56:32 -0700 (PDT) [thread overview]
Message-ID: <660cef90.250a0220.b0d73.354fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240402215502.278838-31-stephen@networkplumber.org>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139064
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, April 02 2024 21:50:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139035-139064 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29695/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-04-03 5:56 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240402215502.278838-31-stephen@networkplumber.org>
2024-04-02 21:37 ` |SUCCESS| pw139035-139064 [PATCH v3 30/30] examples: replace use of fixed size rte_memcpy qemudev
2024-04-02 21:41 ` qemudev
2024-04-02 22:00 ` |WARNING| pw139064 " checkpatch
2024-04-02 23:05 ` |SUCCESS| " 0-day Robot
2024-04-03 3:34 ` |SUCCESS| pw139035-139064 [PATCH] [v3,30/30] examples: replace use o dpdklab
2024-04-03 3:35 ` dpdklab
2024-04-03 3:36 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:42 ` dpdklab
2024-04-03 3:42 ` dpdklab
2024-04-03 3:43 ` dpdklab
2024-04-03 3:43 ` dpdklab
2024-04-03 3:43 ` dpdklab
2024-04-03 3:44 ` dpdklab
2024-04-03 3:44 ` dpdklab
2024-04-03 3:44 ` dpdklab
2024-04-03 3:45 ` dpdklab
2024-04-03 3:48 ` dpdklab
2024-04-03 3:48 ` dpdklab
2024-04-03 3:49 ` dpdklab
2024-04-03 3:51 ` dpdklab
2024-04-03 3:55 ` dpdklab
2024-04-03 3:56 ` dpdklab
2024-04-03 3:56 ` dpdklab
2024-04-03 3:57 ` dpdklab
2024-04-03 3:57 ` dpdklab
2024-04-03 4:00 ` dpdklab
2024-04-03 4:04 ` dpdklab
2024-04-03 4:05 ` dpdklab
2024-04-03 4:05 ` dpdklab
2024-04-03 4:05 ` dpdklab
2024-04-03 4:11 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:22 ` dpdklab
2024-04-03 4:22 ` dpdklab
2024-04-03 4:22 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:24 ` dpdklab
2024-04-03 4:24 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:32 ` dpdklab
2024-04-03 4:32 ` dpdklab
2024-04-03 4:33 ` dpdklab
2024-04-03 4:40 ` dpdklab
2024-04-03 4:41 ` dpdklab
2024-04-03 4:45 ` dpdklab
2024-04-03 4:46 ` dpdklab
2024-04-03 4:46 ` dpdklab
2024-04-03 4:46 ` dpdklab
2024-04-03 4:50 ` dpdklab
2024-04-03 4:50 ` dpdklab
2024-04-03 4:50 ` dpdklab
2024-04-03 4:51 ` dpdklab
2024-04-03 4:53 ` dpdklab
2024-04-03 4:53 ` dpdklab
2024-04-03 4:53 ` dpdklab
2024-04-03 4:59 ` dpdklab
2024-04-03 5:02 ` dpdklab
2024-04-03 5:03 ` dpdklab
2024-04-03 5:04 ` dpdklab
2024-04-03 5:05 ` dpdklab
2024-04-03 5:14 ` dpdklab
2024-04-03 5:16 ` dpdklab
2024-04-03 5:17 ` dpdklab
2024-04-03 5:32 ` dpdklab
2024-04-03 5:38 ` dpdklab
2024-04-03 5:39 ` dpdklab
2024-04-03 5:56 ` dpdklab [this message]
2024-04-03 7:01 ` dpdklab
2024-04-03 22:23 ` dpdklab
2024-04-03 22:27 ` dpdklab
2024-04-03 23:04 ` dpdklab
2024-04-03 23:44 ` dpdklab
2024-04-03 23:47 ` 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=660cef90.250a0220.b0d73.354fSMTPIN_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).