From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135863-135870 [PATCH] [8/8] net/nfp: simplify the port n
Date: Sun, 14 Jan 2024 19:39:32 -0800 (PST) [thread overview]
Message-ID: <65a4a8f4.920a0220.b370f.9754SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135870
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, January 15 2024 02:54:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39a8b1251b204d3898b4c462184f60bda1b64698
135863-135870 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28861/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-15 3:39 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 3:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 4:07 dpdklab
2024-01-15 6:29 dpdklab
2024-01-15 4:42 dpdklab
2024-01-15 4:27 dpdklab
2024-01-15 4:17 dpdklab
2024-01-15 4:16 dpdklab
2024-01-15 4:10 dpdklab
2024-01-15 4:10 dpdklab
2024-01-15 4:07 dpdklab
2024-01-15 4:05 dpdklab
2024-01-15 4:04 dpdklab
2024-01-15 4:03 dpdklab
2024-01-15 4:01 dpdklab
2024-01-15 4:00 dpdklab
2024-01-15 4:00 dpdklab
2024-01-15 4:00 dpdklab
2024-01-15 3:59 dpdklab
2024-01-15 3:57 dpdklab
2024-01-15 3:57 dpdklab
2024-01-15 3:57 dpdklab
2024-01-15 3:55 dpdklab
2024-01-15 3:55 dpdklab
2024-01-15 3:54 dpdklab
2024-01-15 3:54 dpdklab
2024-01-15 3:53 dpdklab
2024-01-15 3:53 dpdklab
2024-01-15 3:52 dpdklab
2024-01-15 3:52 dpdklab
2024-01-15 3:51 dpdklab
2024-01-15 3:51 dpdklab
2024-01-15 3:50 dpdklab
2024-01-15 3:49 dpdklab
2024-01-15 3:44 dpdklab
2024-01-15 3:44 dpdklab
2024-01-15 3:43 dpdklab
2024-01-15 3:42 dpdklab
2024-01-15 3:41 dpdklab
2024-01-15 3:40 dpdklab
2024-01-15 3:40 dpdklab
2024-01-15 3:40 dpdklab
2024-01-15 3:39 dpdklab
2024-01-15 3:39 dpdklab
2024-01-15 3:39 dpdklab
2024-01-15 3:38 dpdklab
2024-01-15 3:38 dpdklab
2024-01-15 3:37 dpdklab
2024-01-15 3:37 dpdklab
2024-01-15 3:36 dpdklab
2024-01-15 3:36 dpdklab
2024-01-15 3:36 dpdklab
2024-01-15 3:35 dpdklab
2024-01-15 3:35 dpdklab
2024-01-15 3:34 dpdklab
2024-01-15 3:34 dpdklab
2024-01-15 3:34 dpdklab
2024-01-15 3:33 dpdklab
2024-01-15 3:33 dpdklab
2024-01-15 3:33 dpdklab
2024-01-15 3:33 dpdklab
2024-01-15 3:33 dpdklab
2024-01-15 3:32 dpdklab
2024-01-15 3:32 dpdklab
2024-01-15 3:32 dpdklab
2024-01-15 3:32 dpdklab
2024-01-15 3:31 dpdklab
2024-01-15 3:31 dpdklab
2024-01-15 3:30 dpdklab
2024-01-15 3:30 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=65a4a8f4.920a0220.b370f.9754SMTPIN_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).