From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138375 [PATCH] test: fix option block
Date: Thu, 14 Mar 2024 05:15:51 -0700 (PDT) [thread overview]
Message-ID: <65f2ea77.050a0220.a8872.354aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314094626.1068059-1-mingjinx.ye@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138375
_Functional Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thursday, March 14 2024 09:46:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138375 --> 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
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 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/29547/
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-14 12:15 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314094626.1068059-1-mingjinx.ye@intel.com>
2024-03-14 9:47 ` qemudev
2024-03-14 9:51 ` qemudev
2024-03-14 10:06 ` checkpatch
2024-03-14 11:03 ` 0-day Robot
2024-03-14 12:03 ` dpdklab
2024-03-14 12:15 ` dpdklab [this message]
2024-03-14 12:17 ` dpdklab
2024-03-14 12:17 ` dpdklab
2024-03-14 12:18 ` dpdklab
2024-03-14 12:18 ` dpdklab
2024-03-14 12:19 ` dpdklab
2024-03-14 12:20 ` dpdklab
2024-03-14 12:21 ` dpdklab
2024-03-14 12:25 ` dpdklab
2024-03-14 12:25 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:33 ` dpdklab
2024-03-14 12:39 ` dpdklab
2024-03-14 12:48 ` dpdklab
2024-03-14 12:49 ` dpdklab
2024-03-14 12:50 ` dpdklab
2024-03-14 12:55 ` dpdklab
2024-03-14 12:55 ` dpdklab
2024-03-14 12:56 ` dpdklab
2024-03-14 12:56 ` dpdklab
2024-03-14 12:56 ` dpdklab
2024-03-14 12:57 ` dpdklab
2024-03-14 12:57 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:58 ` dpdklab
2024-03-14 12:59 ` dpdklab
2024-03-14 12:59 ` dpdklab
2024-03-14 12:59 ` dpdklab
2024-03-14 12:59 ` dpdklab
2024-03-14 12:59 ` dpdklab
2024-03-14 13:00 ` dpdklab
2024-03-14 13:01 ` dpdklab
2024-03-14 13:01 ` dpdklab
2024-03-14 13:02 ` dpdklab
2024-03-14 13:02 ` dpdklab
2024-03-14 13:02 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:05 ` dpdklab
2024-03-14 13:19 ` dpdklab
2024-03-14 13:20 ` dpdklab
2024-03-14 13:25 ` dpdklab
2024-03-14 13:43 ` dpdklab
2024-03-14 13:49 ` dpdklab
2024-03-14 13:52 ` dpdklab
2024-03-14 14:02 ` dpdklab
2024-03-14 14:11 ` dpdklab
2024-03-14 15:33 ` dpdklab
2024-03-18 6:21 ` dpdklab
2024-03-18 6:57 ` 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=65f2ea77.050a0220.a8872.354aSMTPIN_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).