From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136883 [PATCH] examples/dma: fix max-frame-size cannot b
Date: Mon, 19 Feb 2024 21:06:46 -0800 (PST) [thread overview]
Message-ID: <65d43366.810a0220.7f659.8451SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136883
_Functional Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Tuesday, February 20 2024 02:31:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4aa3ea9d5a17df941fab13a648e69b8de8573992
136883 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29184/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-20 5:06 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 5:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 0:50 dpdklab
2024-02-20 7:02 dpdklab
2024-02-20 6:57 dpdklab
2024-02-20 6:44 dpdklab
2024-02-20 6:30 dpdklab
2024-02-20 6:24 dpdklab
2024-02-20 6:21 dpdklab
2024-02-20 6:20 dpdklab
2024-02-20 6:19 dpdklab
2024-02-20 6:18 dpdklab
2024-02-20 6:11 dpdklab
2024-02-20 6:08 dpdklab
2024-02-20 6:08 dpdklab
2024-02-20 6:07 dpdklab
2024-02-20 6:04 dpdklab
2024-02-20 6:02 dpdklab
2024-02-20 5:59 dpdklab
2024-02-20 5:49 dpdklab
2024-02-20 5:49 dpdklab
2024-02-20 5:47 dpdklab
2024-02-20 5:47 dpdklab
2024-02-20 5:47 dpdklab
2024-02-20 5:47 dpdklab
2024-02-20 5:46 dpdklab
2024-02-20 5:45 dpdklab
2024-02-20 5:45 dpdklab
2024-02-20 5:44 dpdklab
2024-02-20 5:43 dpdklab
2024-02-20 5:43 dpdklab
2024-02-20 5:43 dpdklab
2024-02-20 5:43 dpdklab
2024-02-20 5:38 dpdklab
2024-02-20 5:38 dpdklab
2024-02-20 5:36 dpdklab
2024-02-20 5:35 dpdklab
2024-02-20 5:34 dpdklab
2024-02-20 5:34 dpdklab
2024-02-20 5:34 dpdklab
2024-02-20 5:34 dpdklab
2024-02-20 5:33 dpdklab
2024-02-20 5:33 dpdklab
2024-02-20 5:33 dpdklab
2024-02-20 5:33 dpdklab
2024-02-20 5:32 dpdklab
2024-02-20 5:32 dpdklab
2024-02-20 5:32 dpdklab
2024-02-20 5:32 dpdklab
2024-02-20 5:31 dpdklab
2024-02-20 5:31 dpdklab
2024-02-20 5:31 dpdklab
2024-02-20 5:31 dpdklab
2024-02-20 5:30 dpdklab
2024-02-20 5:28 dpdklab
2024-02-20 5:27 dpdklab
2024-02-20 5:27 dpdklab
2024-02-20 5:27 dpdklab
2024-02-20 5:26 dpdklab
2024-02-20 5:26 dpdklab
2024-02-20 5:25 dpdklab
2024-02-20 5:25 dpdklab
2024-02-20 5:25 dpdklab
2024-02-20 5:24 dpdklab
2024-02-20 5:23 dpdklab
2024-02-20 5:23 dpdklab
2024-02-20 5:23 dpdklab
2024-02-20 5:14 dpdklab
2024-02-20 5:02 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=65d43366.810a0220.7f659.8451SMTPIN_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).