From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136058-136063 [PATCH] [6/6] net/ice: reduce code indent
Date: Tue, 23 Jan 2024 10:42:19 -0800 (PST) [thread overview]
Message-ID: <65b0088b.170a0220.46338.8248SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136063
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, January 23 2024 11:40:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0c4a63ce783f55df6b43e519201474c56b5cce36
136058-136063 --> functional testing pass
Test environment and result as below:
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
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/28937/
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-23 18:42 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 18:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-24 4:05 dpdklab
2024-01-24 3:38 dpdklab
2024-01-23 21:47 dpdklab
2024-01-23 20:46 dpdklab
2024-01-23 20:20 dpdklab
2024-01-23 19:48 dpdklab
2024-01-23 19:46 dpdklab
2024-01-23 19:40 dpdklab
2024-01-23 19:40 dpdklab
2024-01-23 19:40 dpdklab
2024-01-23 19:39 dpdklab
2024-01-23 19:38 dpdklab
2024-01-23 19:37 dpdklab
2024-01-23 19:36 dpdklab
2024-01-23 19:35 dpdklab
2024-01-23 19:35 dpdklab
2024-01-23 19:34 dpdklab
2024-01-23 19:31 dpdklab
2024-01-23 19:30 dpdklab
2024-01-23 19:29 dpdklab
2024-01-23 19:28 dpdklab
2024-01-23 19:28 dpdklab
2024-01-23 19:27 dpdklab
2024-01-23 19:27 dpdklab
2024-01-23 19:27 dpdklab
2024-01-23 19:27 dpdklab
2024-01-23 19:26 dpdklab
2024-01-23 19:24 dpdklab
2024-01-23 19:23 dpdklab
2024-01-23 19:22 dpdklab
2024-01-23 19:22 dpdklab
2024-01-23 19:08 dpdklab
2024-01-23 19:08 dpdklab
2024-01-23 19:07 dpdklab
2024-01-23 19:07 dpdklab
2024-01-23 19:05 dpdklab
2024-01-23 19:05 dpdklab
2024-01-23 19:05 dpdklab
2024-01-23 19:04 dpdklab
2024-01-23 19:04 dpdklab
2024-01-23 19:03 dpdklab
2024-01-23 19:02 dpdklab
2024-01-23 19:01 dpdklab
2024-01-23 19:01 dpdklab
2024-01-23 19:00 dpdklab
2024-01-23 19:00 dpdklab
2024-01-23 18:59 dpdklab
2024-01-23 18:59 dpdklab
2024-01-23 18:58 dpdklab
2024-01-23 18:57 dpdklab
2024-01-23 18:53 dpdklab
2024-01-23 18:46 dpdklab
2024-01-23 18:46 dpdklab
2024-01-23 18:46 dpdklab
2024-01-23 18:45 dpdklab
2024-01-23 18:44 dpdklab
2024-01-23 18:42 dpdklab
2024-01-23 18:41 dpdklab
2024-01-23 18:40 dpdklab
2024-01-23 18:40 dpdklab
2024-01-23 18:39 dpdklab
2024-01-23 18:39 dpdklab
2024-01-23 18:18 dpdklab
2024-01-23 18:18 dpdklab
2024-01-23 18:16 dpdklab
[not found] <20240123114053.172189-7-bruce.richardson@intel.com>
2024-01-23 11:19 ` |SUCCESS| pw136058-136063 [PATCH 6/6] " qemudev
2024-01-23 11:24 ` 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=65b0088b.170a0220.46338.8248SMTPIN_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).