From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138332 [PATCH] [v1,1/1] iavf: document limitation on MTU
Date: Wed, 13 Mar 2024 10:41:56 -0700 (PDT) [thread overview]
Message-ID: <65f1e564.050a0220.42d43.e5a6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <f5310a19f7d9aeb08aa5bf31f19fe59dafadbdd7.1710344183.git.anatoly.burakov@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138332
_Functional Testing PASS_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Wednesday, March 13 2024 15:43:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:19082c1fac430c74bb4b1c101edd12d88928e7c2
138332 --> 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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 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/29536/
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-03-13 17:41 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f5310a19f7d9aeb08aa5bf31f19fe59dafadbdd7.1710344183.git.anatoly.burakov@intel.com>
2024-03-13 15:23 ` |SUCCESS| pw138332 [PATCH v1 1/1] " qemudev
2024-03-13 15:27 ` qemudev
2024-03-13 15:45 ` checkpatch
2024-03-13 16:43 ` 0-day Robot
2024-03-13 17:41 ` dpdklab [this message]
2024-03-13 17:42 ` |SUCCESS| pw138332 [PATCH] [v1,1/1] " dpdklab
2024-03-13 17:42 ` dpdklab
2024-03-13 17:42 ` dpdklab
2024-03-13 17:42 ` dpdklab
2024-03-13 17:43 ` dpdklab
2024-03-13 17:43 ` dpdklab
2024-03-13 17:43 ` dpdklab
2024-03-13 17:43 ` dpdklab
2024-03-13 17:43 ` dpdklab
2024-03-13 17:44 ` dpdklab
2024-03-13 17:44 ` dpdklab
2024-03-13 17:44 ` dpdklab
2024-03-13 17:44 ` dpdklab
2024-03-13 17:45 ` dpdklab
2024-03-13 17:45 ` dpdklab
2024-03-13 17:45 ` dpdklab
2024-03-13 17:46 ` dpdklab
2024-03-13 17:46 ` dpdklab
2024-03-13 17:46 ` dpdklab
2024-03-13 17:47 ` dpdklab
2024-03-13 17:47 ` dpdklab
2024-03-13 17:47 ` dpdklab
2024-03-13 17:48 ` dpdklab
2024-03-13 17:48 ` dpdklab
2024-03-13 17:48 ` dpdklab
2024-03-13 17:49 ` dpdklab
2024-03-13 17:49 ` dpdklab
2024-03-13 17:49 ` dpdklab
2024-03-13 17:49 ` dpdklab
2024-03-13 17:49 ` dpdklab
2024-03-13 17:50 ` dpdklab
2024-03-13 17:50 ` dpdklab
2024-03-13 17:50 ` dpdklab
2024-03-13 17:50 ` dpdklab
2024-03-13 17:51 ` dpdklab
2024-03-13 17:51 ` dpdklab
2024-03-13 17:51 ` dpdklab
2024-03-13 17:51 ` dpdklab
2024-03-13 17:52 ` dpdklab
2024-03-13 17:52 ` dpdklab
2024-03-13 17:52 ` dpdklab
2024-03-13 17:53 ` dpdklab
2024-03-13 17:53 ` dpdklab
2024-03-13 17:53 ` dpdklab
2024-03-13 17:53 ` dpdklab
2024-03-13 17:53 ` dpdklab
2024-03-13 17:53 ` dpdklab
2024-03-13 17:54 ` dpdklab
2024-03-13 17:54 ` dpdklab
2024-03-13 17:54 ` dpdklab
2024-03-13 17:55 ` dpdklab
2024-03-13 17:55 ` dpdklab
2024-03-13 17:55 ` dpdklab
2024-03-13 17:55 ` dpdklab
2024-03-13 17:55 ` dpdklab
2024-03-13 17:56 ` dpdklab
2024-03-13 17:56 ` dpdklab
2024-03-13 17:56 ` dpdklab
2024-03-13 17:57 ` dpdklab
2024-03-13 17:58 ` dpdklab
2024-03-13 17:59 ` dpdklab
2024-03-13 17:59 ` dpdklab
2024-03-13 18:00 ` dpdklab
2024-03-13 18:02 ` dpdklab
2024-03-13 18:10 ` dpdklab
2024-03-13 18:14 ` dpdklab
2024-03-13 18:15 ` dpdklab
2024-03-13 18:18 ` dpdklab
2024-03-13 18:51 ` dpdklab
2024-03-17 8:28 ` dpdklab
2024-03-17 9:04 ` 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=65f1e564.050a0220.42d43.e5a6SMTPIN_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).