From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135213 [PATCH] [v4,3/7] dts: add optional packet filteri
Date: Thu, 14 Dec 2023 19:48:19 -0800 (PST) [thread overview]
Message-ID: <657bcc83.c80a0220.df9ac.ab1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135213
_Functional Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Thursday, December 14 2023 22:10:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135213 --> functional testing pass
Test environment and result as below:
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
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/4
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28635/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-15 3:48 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 3:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 15:28 dpdklab
2023-12-15 7:51 dpdklab
2023-12-15 6:44 dpdklab
2023-12-15 6:38 dpdklab
2023-12-15 6:34 dpdklab
2023-12-15 6:06 dpdklab
2023-12-15 5:44 dpdklab
2023-12-15 5:44 dpdklab
2023-12-15 5:43 dpdklab
2023-12-15 5:38 dpdklab
2023-12-15 5:36 dpdklab
2023-12-15 5:35 dpdklab
2023-12-15 5:30 dpdklab
2023-12-15 5:29 dpdklab
2023-12-15 5:28 dpdklab
2023-12-15 5:27 dpdklab
2023-12-15 5:27 dpdklab
2023-12-15 5:27 dpdklab
2023-12-15 5:26 dpdklab
2023-12-15 5:26 dpdklab
2023-12-15 5:23 dpdklab
2023-12-15 5:22 dpdklab
2023-12-15 5:22 dpdklab
2023-12-15 5:12 dpdklab
2023-12-15 5:11 dpdklab
2023-12-15 5:08 dpdklab
2023-12-15 5:07 dpdklab
2023-12-15 5:05 dpdklab
2023-12-15 5:02 dpdklab
2023-12-15 4:58 dpdklab
2023-12-15 4:58 dpdklab
2023-12-15 4:58 dpdklab
2023-12-15 4:58 dpdklab
2023-12-15 4:57 dpdklab
2023-12-15 4:57 dpdklab
2023-12-15 4:57 dpdklab
2023-12-15 4:56 dpdklab
2023-12-15 4:56 dpdklab
2023-12-15 4:54 dpdklab
2023-12-15 4:49 dpdklab
2023-12-15 4:49 dpdklab
2023-12-15 4:47 dpdklab
2023-12-15 4:47 dpdklab
2023-12-15 4:46 dpdklab
2023-12-15 4:45 dpdklab
2023-12-15 4:45 dpdklab
2023-12-15 4:44 dpdklab
2023-12-15 4:43 dpdklab
2023-12-15 4:42 dpdklab
2023-12-15 4:39 dpdklab
2023-12-15 4:38 dpdklab
2023-12-15 4:38 dpdklab
2023-12-15 4:35 dpdklab
2023-12-15 4:34 dpdklab
2023-12-15 4:33 dpdklab
2023-12-15 4:29 dpdklab
2023-12-15 4:23 dpdklab
2023-12-15 4:21 dpdklab
2023-12-15 4:16 dpdklab
2023-12-15 4:13 dpdklab
2023-12-15 4:12 dpdklab
2023-12-15 4:01 dpdklab
2023-12-15 3:52 dpdklab
2023-12-15 3:50 dpdklab
2023-12-15 3:48 dpdklab
2023-12-15 3:47 dpdklab
2023-12-15 3:41 dpdklab
2023-12-15 3:36 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=657bcc83.c80a0220.df9ac.ab1fSMTPIN_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).