From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126101-126122 [PATCH] [v2, 22/22] test/pdcp: add PDCP status report cases
Date: Sat, 15 Apr 2023 05:08:44 +0000 (UTC) [thread overview]
Message-ID: <20230415050844.C31F06008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126122
_Functional Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Friday, April 14 2023 17:45:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126101-126122 --> 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/2
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/2
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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/26005/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-15 5:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 5:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-15 9:39 dpdklab
2023-04-15 9:05 dpdklab
2023-04-15 6:23 dpdklab
2023-04-15 5:29 dpdklab
2023-04-15 5:23 dpdklab
2023-04-15 5:03 dpdklab
2023-04-15 4:58 dpdklab
2023-04-15 4:53 dpdklab
2023-04-15 4:49 dpdklab
2023-04-14 22:26 dpdklab
2023-04-14 22:21 dpdklab
2023-04-14 22:16 dpdklab
2023-04-14 22:13 dpdklab
2023-04-14 22:09 dpdklab
2023-04-14 22:08 dpdklab
2023-04-14 22:06 dpdklab
2023-04-14 22:03 dpdklab
2023-04-14 21:58 dpdklab
2023-04-14 21:55 dpdklab
2023-04-14 21:50 dpdklab
2023-04-14 21:49 dpdklab
2023-04-14 21:43 dpdklab
2023-04-14 21:41 dpdklab
2023-04-14 21:25 dpdklab
2023-04-14 21:08 dpdklab
2023-04-14 21:05 dpdklab
2023-04-14 20:52 dpdklab
2023-04-14 20:49 dpdklab
2023-04-14 20:47 dpdklab
2023-04-14 20:39 dpdklab
2023-04-14 20:39 dpdklab
2023-04-14 20:34 dpdklab
2023-04-14 20:33 dpdklab
2023-04-14 20:32 dpdklab
2023-04-14 20:31 dpdklab
2023-04-14 20:26 dpdklab
2023-04-14 20:25 dpdklab
2023-04-14 20:18 dpdklab
2023-04-14 20:15 dpdklab
2023-04-14 20:06 dpdklab
2023-04-14 20:06 dpdklab
2023-04-14 20:02 dpdklab
2023-04-14 20:02 dpdklab
2023-04-14 20:00 dpdklab
2023-04-14 19:59 dpdklab
2023-04-14 19:58 dpdklab
2023-04-14 19:56 dpdklab
[not found] <20230414174512.642-23-anoobj@marvell.com>
2023-04-14 17:38 ` |SUCCESS| pw126101-126122 [PATCH v2 " qemudev
2023-04-14 17:42 ` qemudev
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=20230415050844.C31F06008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).