From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136304 [PATCH] net/cnxk: fix aged flows query
Date: Fri, 02 Feb 2024 00:34:10 -0800 (PST) [thread overview]
Message-ID: <65bca902.050a0220.a1a9.3c77SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136304
_Functional Testing PASS_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Friday, February 02 2024 05:21:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7d3daa3988e6b0216ace4ad882f3ccf1664cc7a7
136304 --> 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/29030/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 8:34 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 13:13 dpdklab
2024-02-02 12:39 dpdklab
2024-02-02 12:09 dpdklab
2024-02-02 9:55 dpdklab
2024-02-02 9:55 dpdklab
2024-02-02 9:36 dpdklab
2024-02-02 9:34 dpdklab
2024-02-02 9:32 dpdklab
2024-02-02 9:32 dpdklab
2024-02-02 9:25 dpdklab
2024-02-02 9:24 dpdklab
2024-02-02 9:24 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:23 dpdklab
2024-02-02 9:18 dpdklab
2024-02-02 9:18 dpdklab
2024-02-02 9:17 dpdklab
2024-02-02 9:16 dpdklab
2024-02-02 9:15 dpdklab
2024-02-02 9:14 dpdklab
2024-02-02 9:09 dpdklab
2024-02-02 9:09 dpdklab
2024-02-02 9:08 dpdklab
2024-02-02 9:08 dpdklab
2024-02-02 9:07 dpdklab
2024-02-02 9:06 dpdklab
2024-02-02 9:06 dpdklab
2024-02-02 9:05 dpdklab
2024-02-02 9:05 dpdklab
2024-02-02 9:05 dpdklab
2024-02-02 9:04 dpdklab
2024-02-02 9:03 dpdklab
2024-02-02 9:03 dpdklab
2024-02-02 9:02 dpdklab
2024-02-02 9:01 dpdklab
2024-02-02 9:01 dpdklab
2024-02-02 9:00 dpdklab
2024-02-02 8:59 dpdklab
2024-02-02 8:56 dpdklab
2024-02-02 8:55 dpdklab
2024-02-02 8:54 dpdklab
2024-02-02 8:54 dpdklab
2024-02-02 8:52 dpdklab
2024-02-02 8:44 dpdklab
2024-02-02 8:43 dpdklab
2024-02-02 8:39 dpdklab
2024-02-02 8:37 dpdklab
2024-02-02 8:14 dpdklab
2024-02-02 7:57 dpdklab
2024-02-02 7:47 dpdklab
2024-02-02 7:27 dpdklab
2024-02-02 7:25 dpdklab
2024-02-02 7:21 dpdklab
2024-02-02 7:16 dpdklab
2024-02-02 7:07 dpdklab
2024-02-02 7:03 dpdklab
2024-02-02 6:58 dpdklab
2024-02-02 6:56 dpdklab
2024-02-02 6:56 dpdklab
2024-02-02 6:56 dpdklab
2024-02-02 6:54 dpdklab
2024-02-02 6:53 dpdklab
2024-02-02 6:53 dpdklab
2024-02-02 6:52 dpdklab
2024-02-02 6:51 dpdklab
2024-02-02 6:49 dpdklab
[not found] <20240202052137.1324084-1-psatheesh@marvell.com>
2024-02-02 4:59 ` qemudev
2024-02-02 5:03 ` qemudev
2024-02-02 5:22 ` checkpatch
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=65bca902.050a0220.a1a9.3c77SMTPIN_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).